From: Emmanuel d'O. <ed...@ab...> - 2008-02-28 15:40:09
|
Dear all, I was hoping that some of you may share their insights on this topic I'm documenting: Problem: Allowing concurrent atomic edits of an xml document in eXist from multiple users using a web browser. Example: A planning is stored as a single XML document in eXist. At any given time it contains 1000+ events, each containing a number of children (date, time, location, resources, comments, links, etc). The planning goes through only minor XSL transformations to be displayed in the browser and could almost be stored as plain XHTML in eXist. Almost every value of the document can be updated/created/deleted in the browser using javascript and these values are then sent back to eXist. The structure of the document on the server may have changed in the meantime. Question: What is the best way to identify the node that has been updated between the browser and the server: unique ids on all editable elements? Is there any other way to test identity between client and server? Many thanks in advance, Emmanuel PS: Conflicting edits is another topic. |