[opencms-dev] OpenCms in the future?

[Lambert Gerard]

Hello, 
thanks Andrea for the remarks and the tests.  
The purpose of the first version of script postgres was to map all index from the mysql database.
I made the changes suggested and withdrawn index which seemed useless to me (on the keys and included in others index).
Here a cleaned version.

The order in the script is the same as in the mysql script

Gérard

esnig
Ecole Supérieure Neuchâteloise d'Informatique de Gestion 
Maladière 84,
CH-2000 Neuchâtel
tél: +41 (0)32 717 4231



-----Message d'origine-----
De : opencms-dev-bounces at opencms.org
[mailto:opencms-dev-bounces at opencms.org]De la part de Andreas Haumer
Envoyé : jeudi, 15. septembre 2005 10:43
À : The OpenCms mailing list
Objet : Re: [opencms-dev] OpenCms in the future?


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Alexander!

Alexander Kandzior schrieb:
| Joe,
|
| regarding our development roadmap for OpenCms, there are 3 lists of
| features:
|
| 1. Stuff already finished (or to be finished soon)
|
[...]
|
| 2. Stuff in the pipeline (requested by paying clients)
|
[...]
|
| 3. Stuff we would like to work on in the future
|
[...]

Thanks for this mail. I was already looking for a roadmap for
OpenCMS in the past but didn't find a document describing your
plans and ideas about the future development of OpenCMS. IMHO
for a successful open source project it is important for the
community to know where the main developers are heading, so
that potential new developers find a place where they can
work on. Otherwise, OSS projects tend to become more like a
"one-way" development effort, which might be quite frustrating
for the main contributors (that is, if the main developers want
new developers to participate anyway, of course)

That being said, I'd like to bring up again a subject I have
already mentioned on the list several times, but without any
reply so far: Caching at the DB access layer! As I tried to
explain I think that it might help to improve the performance
of OpenCMS quite noticable and reduce the load on the RDBMS at
the same time. DB access cache is an important and widely used
technique for DB applications in general and especially for web
applications. If done right, the advantages usually are considerable!

Did anyone read my mails?
What do you think about this?
Is something like that already on your roadmap?
Did you already try to implement a DB access cache layer?
Would that be an area where one could contribute to OpenCMS
according to the roadmap of the main developers?

As my mails on this subject were completely ignored so far,
I got the impression that there is no interest. If that is
the case, please do give me a short note and I'll shut up
forever (on this issue, that is... ;-)

Comments?

- - andreas

- --
Andreas Haumer                     | mailto:andreas at xss.co.at
*x Software + Systeme              | http://www.xss.co.at/
Karmarschgasse 51/2/20             | Tel: +43-1-6060114-0
A-1100 Vienna, Austria             | Fax: +43-1-6060114-71
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDKTQRxJmyeGcXPhERAkXUAKCtGyvQgzjCqItEnTbckVQDk4BHlgCeI7bB
dRsB9tVHUl1NkTLjWDRnIks=
=QmSx
-----END PGP SIGNATURE-----


_______________________________________________
This mail is send to you from the opencms-dev mailing list
To change your list options, or to unsubscribe from the list, please visit
http://mail.opencms.org/mailman/listinfo/opencms-dev
-------------- next part --------------
A non-text attachment was scrubbed...
Name: create_tables_v2.sql
Type: application/octet-stream
Size: 15578 bytes
Desc: create_tables_v2.sql
URL: <https://webmail.opencms.org/pipermail/opencms-dev/attachments/20050916/413a68e6/attachment.obj>