Hi Lenya devs,

during the weekend I had an idea which first seemed too unorthodox to mention, but maybe it can start a fruitful discussion.

There's one critical issue in 2.0 which bothers me: The size of continuations. In the docu publication, an instance of the sitetree occupies about 10 MB of heap space. Since it is duplicated as soon as it is requested by a modifiable session (i.e., in a usecase which is about to be executed), the continuations grow very large. When you click "Publish" for 20 documents in a row in the MultiWorkflow usecase, quite a lot of RAM is allocated.

There are multiple ways to approach this problem:

1. Break the sitetree up in local collections/indexes (I think this is what solprovider implemented in 1.3, and I like the idea a lot).

2. Don't duplicate the whole sitetree, but only the affected fragments, and merge them back into the tree when the session is committed (nice idea, but probably very complicated when it comes to implementation).

3. Get rid of the live sitetree, move sitetree features to meta data.


In case 3, the sitetree would only be a skeleton to declare the parent-child relations of documents. The navigation title and visibility would be stored in the document's meta data. This way, publishing and deactivating wouldn't affect the sitetree at all. The sitetree would only have to be checked out during operations which directly manipulate the document hierarchy: Adding/deleting documents and cut/copy/paste.

Another positive side effect would be that there can't be any checked-out live sitetrees anymore (see bug 44563, thanks to Richard for the check-in workaround).

Additionally, it would be possible to change the document hierarchy (cut/copy/paste, move up, move down) without deactivating the corresponding documents. Of course, the changes would be live immediately, but maybe the users could live with that. Deactivating a document before moving it around in the sitetree also affects the public site.


I hope we can collect some fresh ideas to improve the site structure implementation.

solprovider, I would be very interested in a short overview on your site structure / index ideas. Sorry if you have already posted this - if you remember the title, would you mind giving a pointer to the archive? Thanks a lot in advance!


-- Andreas


--
Andreas Hartmann, CTO
BeCompany GmbH
http://www.becompany.ch
Tel.: +41 (0) 43 818 57 01


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to