> > For what it's worth, I'd just go to the direct save route. People > are working directly against databases with a lot of software, and > none of it give you the "undo/redo" ability of a desktop app without > much complaints. Good point.
> > Wait... what did I just say? Undo/redo huh? We _could_ in fact store > on the disk a list of commands that morph the catalog and allow > people to actually undo their changes... that would be a first for > server side apps. And of course, it assumes a single admin model, or > else, we'd have to mark changes with the user that performed them > (with the new security subsystem any user can have the ROLE_ADMNISTRATOR > role). Hmmm... i like it... I like it a lot. Doing everything in a command not only gives us undo / redo it would also allow the rest stuff to use a lot of the same logic and avoid duplication. Go Andrea, you win a puppet :). > > Cheers > Andrea > > !DSPAM:4007,486244e433961012714783! > -- Justin Deoliveira The Open Planning Project [EMAIL PROTECTED] ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
