Atom and Optimistic Concurrency
Elias illustrates some thoughts about optimistic concurrency control and announces that Queso now implements OCC...
What does OCC as described by Google gives us? In my opinion, it takes Atom Protocol implementors (client and server) closer to a level where they can start thinking about merge procedures but they are not there yet.
The post reminded me of several questions I had when Google announced GData that I need to follow up on. If anybody has thoughts, please post.
- What is the ideal concurrency control as a service provider when the client cannot be controlled?
- What type of merge procedures can be generalized for Atom?