> [1a] The wizard schema is read and maintained in memory for every user that > logs on - even if they use the same wizard. It woud make more sense if > there would be a 'xml reader' class associated with the wizards. Thsi class > can read teh xmls (and probably cache them), and pass them to wizards that > need it. Everey user session will then have a refernce to a wizard > retrieved by the reader, but since the wizard is not 'created' by the user > session, more users can use the same instance of the wizard tree. In > addition, by caching wizards, loading the xml can be sped up.
I have no problem with that' do we want the standard xml reader to cache doms? > [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?). this is a prolbem that needs to be solved in the core (if we want to solve it) so i thing it is ok to remove the "referance" original data and modify the dove servlet. >A wizard ProcessorModule class could be a way to implement this (as it can > be read from the bridge, and allows customization through the admin pages). -1 for that . we now have the config/utils directory with the coresponding xml reader. creating a "processor" module won't make thing easyer or nicer INHO
