reading the couchdb book, I came across the statement,
"Writes are serialized, allowing only one write operation at any point in time, for any single database"
what does this mean? how does it control write conflict without locks? This is probably a question better suited to the couchdb mailing list, but I wanted a more computer science explanation of it than a 'product' explanation.
thank you
Once a write is performed, the revision number for that document is changed. If a write comes in with an older revision number, it is kicked back with an error telling the application/user to review their changes against the most recent document in question before resubmitting their new version.
Now, when you're dealing with multiple nodes, there is some conflict management that will need to occur on the CouchDB document, refer to this chapter for an explanation of that process: http://books.couchdb.org/relax/reference/conflict-management
