> I haven't needed transactions or record versioning in my applications. > I'm amenable to MiddleKit enhancements in this area, however.
I'm going to build an abstract VersionedObject MiddleKit object class next week because I need one for a wiki-esque application where users can change each others contributions. If someone has a) interest in seeing the results or b) some thoughts on the subject / links to similar projects that might make this task easier, please keep me posted. First thoughts: * the VersionedObject should have a method "versions()", returning a list of past versions. A "delta view" showing the differences between two objects can be easily built using libdiff * the VersionedObject should have a method "newVersion" that has to be triggered before any changes that lead to a new version are made. Changes to the object that don't lead to a new version should be possible. * two kinds of references to the VersionedObject should be possible: one referring to "the most current version", this is the default object reference consisting of Klass ID and serialNum that MiddleKit uses anyway. The second reference is to a specific version of the VersionedObject, which uses the default object reference plus the version number * all this would imply that "old versions" of objects are really just new copies that are saved of an VersionedObject. They should probably have a timestamp. -- Martin Virtel [EMAIL PROTECTED] aim / yahoo messenger mvftd tel. +49 177 242 2889 ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
