Zope takes a pretty optimistic approach to dealing with conflicting database changes. Sometimes, there may be "hot spots" in an application that get a lot of simultaneous writes. These hot spots can often be designed away. An alternative is to provide application-level logic for sorting out the changes made by conflicting writes. The proposed interface at: http://www.zope.org/Members/jim/ZODB/ApplicationLevelConflictResolution provides a way to provide this application logic. Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! Technical Director (888) 344-4332 http://www.python.org Digital Creations http://www.digicool.com http://www.zope.org Under US Code Title 47, Sec.227(b)(1)(C), Sec.227(a)(2)(B) This email address may not be added to any commercial mail list with out my permission. Violation of my privacy with advertising or SPAM will result in a suit for a MINIMUM of $500 damages/incident, $1500 for repeats. _______________________________________________ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
