[cvs] [Wiki] changed: Project/ResourceLocking

[Ben Klang]

bklang  Sun, 10 Aug 2008 19:32:08 -0400

Modified page: http://wiki.horde.org/Project/ResourceLocking
New Revision:  1.15
Change log:  It's now August

@@ -15,9 +15,9 @@
  > **Locking** The easy one is to lock an item for a certain time  
when someone starts to edit it. If someone else trys to edit it Horde  
will deny this and tell the user to wait. The disadvantage of this is  
that only one person can edit one item at one time which on a popular  
system may be cumbersome.  However there is additionally the concept  
of a "shared" lock which may be useful with the next strategy.

  > **Try to merge** An improved approach would be to allow Horde  
applications to try to merge the changes two users make similar to  
source control software. If changes cannot be merged automatically  
Horde will notify the user. Horde_Lock will make no attempt to  
implement merging as this is highly application specific but is  
designed to allow applications to use the shared lock concept in  
concert with a merging strategy.

-+++ Project Status - May 2008
++++ Project Status - August 2008
  > Since a mechanism is needed to lock resources for full !WebDAV  
functionality a new Horde_Lock subsystem has been merged into Horde  
3.2.  This subsystem is capable of locking arbitrary resources  
identified by URI and grouped by scope.  The locks support timeouts  
and exclusive vs. shared semantics.

  +++ The API
  > The API has been published in the Horde API documentation.  Anyone  
interested in this project is invited to review the following URL and  
provide feedback to the Horde Dev mailing list.