<< 1 is it not a good idea to store all this data in de database for the
length of their use? i can imagine the memory use weighs more than the
database overhead >>
I don't think so. You would rather not store temporary data in a database.
<< 2 am i right those form xml's don't change till the wizard is being
altered (like jsp's) , can't they be cached? >>
form xmls are a combination of data-being-edited with the wizard sceham. They change with every invocation of te wizard (in fact, they are re-created with every call).
<< 2 is it not a good idea to add checkout function to nodes? this will
allso make things easyer? >>
There is a sort of thing like that (not really checkout, but you can make 'temporary'nodes for editing). The main problem of a checkout system is that this works on one machine only: if you use two servers, they are unaware of ecach others edits. You might solve that using multicast, but there is a delay, so it's not really safe.
You also need to determine when to release a lock in case someone aborts a session without properly closing the transaction (either in the editwizards or another editor). I.e. in the editwizards a session can last an hour - which means a 'lock' could conceivably last the same length if someone aborts his editor by (for isnatnce) closing his browser.
Pierre
