W3C home > Mailing lists > Public > ietf-dav-versioning@w3.org > April to June 2008

Conflict detection in DeltaV using ServerSide Workspace

From: <M.Jung@dlr.de>
Date: Tue, 24 Jun 2008 13:11:02 +0200
Message-ID: <EA5B35EEE31E4B4E89473B9EA0905C4DA4BF78@exbe02.intra.dlr.de>
To: <ietf-dav-versioning@w3.org>


I want to allow simultaneous editing of resources by multiple users with
WebDAV/DeltaV. For that, I use a ServerSide-Workspace for every user.
The user can "check out" a file in his private workspace and work on it.
After that, the user can "check in" all of his files with the DeltaV
activity feature. Now I am looking for a standard "serverside"-way to
detect conflicts when both users try to commit their changes on the same
file. Is there any standard way to detect these conflicts with
WebDAV/DeltaV on serverside?

My idea was (like in Subversion/mod_dav_svn), that the server keeps
track of the revisions, that are in the private workspace of the user,
to detect conflicts. 

Here you can see a sequence diagram that illustrates the operations. 


User A and user B check out the file Foo. The server keeps track that
they both checked out version 1 of the file Foo. Now both users start to
edit the file in their own workspace. Then user A finishes editing and
checks in his workspace (ActivityUserA). Now the server increments the
version of file Foo up to 2. Now user B wants to check in his file, but
the server recognizes that UserB has changed the file based on version 1
and so the server rejects the check in. 

Is this the right way? 

Thank you for your Help.

Best regards


Martin Jung
master student

DLR (German Aerospace Center), 
Simulation and Software Technology
Linder Hoehe, 51147 Cologne, Germany

eMail: m.jung at dlr.de http://www.dlr.de/sc
Received on Tuesday, 24 June 2008 11:14:06 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:55:49 UTC