http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660The server rejecting an update does not translate into the user experience. It is up to the client code to know how to handle this rejection in a user pleasing and business logic acceptable way. http://ayende.com/3900/designing-a-document-database-concurrency#comment8http://ayende.com/3900/designing-a-document-database-concurrency#comment8Tue, 10 Mar 2009 17:21:05 GMTok. guess I was throwing partial updates in there too. If the user experience of requiring the document to be reloaded if its not the latest before accepting changes is acceptable, then good. it is, by far, much easier to implement. http://ayende.com/3900/designing-a-document-database-concurrency#comment7http://ayende.com/3900/designing-a-document-database-concurrency#comment7Tue, 10 Mar 2009 16:02:10 GMTI am not sure that I understand what you mean. What I intend to do is actually create a very simple system. If you update a document with a version that is not the latest, I am going to reject the update. http://ayende.com/3900/designing-a-document-database-concurrency#comment6http://ayende.com/3900/designing-a-document-database-concurrency#comment6Tue, 10 Mar 2009 15:56:45 GMTso you track what changes on the client/app side, and send only those changes with the relevant version? http://ayende.com/3900/designing-a-document-database-concurrency#comment5http://ayende.com/3900/designing-a-document-database-concurrency#comment5Tue, 10 Mar 2009 15:50:36 GMTNo, I do not. I track this at field level. This something like the way SVN track those changes. http://ayende.com/3900/designing-a-document-database-concurrency#comment4http://ayende.com/3900/designing-a-document-database-concurrency#comment4Tue, 10 Mar 2009 15:44:55 GMTSo do you version at the record/document level or at the field level? Assuming you want to merge changes without overwriting someone else's update, you need a way to determine what changed at the field level. Maybe you don't care that much, or just make a user reload the latest version before allowing them to commit changes (which can be a bad user experience). http://ayende.com/3900/designing-a-document-database-concurrency#comment3http://ayende.com/3900/designing-a-document-database-concurrency#comment3Tue, 10 Mar 2009 15:35:47 GMTNo, I mean that you know what version a document is, useful for things like optimistic concurrency. http://ayende.com/3900/designing-a-document-database-concurrency#comment2http://ayende.com/3900/designing-a-document-database-concurrency#comment2Tue, 10 Mar 2009 12:12:00 GMTWhen you say versioned, do you mean that we can rewind/fast forward in time to a particular version? http://ayende.com/3900/designing-a-document-database-concurrency#comment1http://ayende.com/3900/designing-a-document-database-concurrency#comment1Tue, 10 Mar 2009 12:03:43 GMT