[cvs] [Wiki] changed: Project/ResourceLocking

Ben Klang ben at alkaloid.net
Wed May 7 14:52:38 UTC 2008


bklang  Wed, 07 May 2008 10:52:37 -0400

Modified page: http://wiki.horde.org/Project/ResourceLocking
New Revision:  1.12
Change log:  Dewikify, formatting

@@ -14,19 +14,19 @@

 > **Try to merge** The better way would be that Horde trys 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 - May 2008
-> Since I needed a mechanism to lock resources for full WebDAV
functionality I have written a Horde_Lock subsystem.  The work to date has
been committed to Horde CVS HEAD.  This subsystem is capable of locking
arbitrary resources identified by URI.  The locks support timeouts and
exclusive vs. shared semantics.
+> Since I needed a mechanism to lock resources for full !WebDAV
functionality I have written a Horde_Lock subsystem.  The work to date has
been committed to Horde CVS HEAD.  This subsystem is capable of locking
arbitrary resources identified by URI.  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.
-http://dev.horde.org/api/framework/Horde_Lock/Horde_Lock.html
+> http://dev.horde.org/api/framework/Horde_Lock/Horde_Lock.html

 +++ TODO

 * Stabilize SQL driver
-* Implement all semantics required to be RFC-compliant for WebDAV locks,
with an eye toward using these locks in other Horde applications.
+* Implement all semantics required to be RFC-compliant for !WebDAV locks,
with an eye toward using these locks in other Horde applications.

 +++ Wishlist
 > These are potential uses for the Lock system that have been requested or
proposed by others.


More information about the cvs mailing list