On Fri, Jan 23, 2004 at 11:36:24AM -0500, Casey Duncan wrote:
<a big long explanation>
Thanks, this is much clearer now.
Conflicts tend to center around "hotspots", objects that are changed often by many requests. The Catalog is a classic example since it tends to get changed everytime new content is added to the system. Content repository folders are another example.
Both of these "hotspots" have their own conflict resolution code (they typically use BTree objects which can resolve many write conflicts internally). Write conflicts tend to be pretty manageable if you recognize hotspots and use the proper data types (like BTrees) or add your own conflict resolution (not for the faint of heart, however).
Where can I read about writing my own conflict resolution? What risks are there with this approach, and how do I minimize them? srl -- Shane Landrum, Software Engineer srl@boston.com boston.com / NY Times Digital