[cvs] [Wiki] changed: Project/ResourceLocking

Ben Klang ben at alkaloid.net
Tue May 6 04:37:16 UTC 2008


bklang  Tue, 06 May 2008 00:37:14 -0400

Modified page: http://wiki.horde.org/Project/ResourceLocking
New Revision:  1.9
Change log:  update project status

@@ -8,8 +8,11 @@

 +++ Two ways

 > There are (a least) two ways how this can be done. **Locking** The easy
one is to lock an item for a certain time when someone starts to edit it. If
someone else tryes to edit it, horde will deny this and tell him / her to
wait. The contra of this is that only one person can edit one item at one
time (not very good for a groupware). **Try to merge** The better way would
be that horde tryes to merge the changes, similar to cvs. If changes cannot
be merged, horde will tell the user. I think this is what I'll try.
+
++++ New Work
+> Since I needed a mechanism to lock resources for full WebDAV
functionality I have written a Horde_Lock subsystem.  Hopefully it will be
in CVS HEAD soon.  This subsystem is capable of locking arbitrary resources
identified by URI.  The locks support timeouts and exclusive vs. shared
semantics.

 +++ TODO

 * write Text_Patch to use diff's from Text_Diff
@@ -17,9 +20,10 @@
 * add Method to merge Data
 * do test implementaion in nag

 +++ Timeline
-* June, 06th 2005 Idea for this project
-* June, 24th 2005 add TODO, start coding
+* June 6th, 2005 Idea for this project
+* June 24th, 2005 add TODO, start coding
+* May 5th, 2008 Project ownership moved to Ben Klang

 +++ Contact
-> Martin Lohmeier <martin AT mein-horde.de>
+> Ben Klang <ben at alkaloid.net>


More information about the cvs mailing list