[...]
[1c] Since MMBase has no locking mechanism, the wizard maintains a 'original data' xml tree. The Dove uses this tree to validate changes (so if someone changes the object, the wizard issues an error). Perhaps a less memory-consuming way can be found to check on changes in an object (so the original data tree is not needed), but I gather this would either require versioning (or 'last modified dates'), or another method to make comparison easy (hashcodes?).
All nodes in MMBase have at least two fields: number and owner. These are deeply rooted in the core but is it not worth investigating to add an extra field 'updated' or 'modified'? Or would that involve a complete rewrite of MMBase?
Nodes could be checked out and tagged with the last modified date. And when they are checked in again they can be checked against the last modified date in the database.
---Andr�
------------------------------------------->><<--------- Andr� van Toly http://www.toly.nl 06-27233562
