[Wiki] changed: Project/ResourceLocking

Ben Klang <[email protected]>
Newsgroups gmane.comp.horde.cvs
Message-ID <[email protected]>
bklang  Sun, 10 Aug 2008 13:55:16 -0400

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

@@ -21,18 +21,19 @@

  +++ 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
+
++++ Completed Tasks
+* The SQL driver is complete and integrated and was released with Horde 3.2
+* All semantics necessary to support !WebDAV locks are complete.  A  
partial implementation has been released with Horde_RPC_webdav class  
that was released with Horde 3.2.

  +++ TODO
-
-* Stabilize SQL driver (mostly done, more testing is necessary)
-* Implement all semantics required to be RFC-compliant for !WebDAV  
locks, with an eye toward using these locks in other Horde  
applications. (Done and implemented in Horde_RPC_webdav class)
+* Implement administrator's UI that lists all active locks with the  
ability to delete stale and/or arbitrary locks.
+* Extend Wicked to take advantage of Horde_Lock (caution: Maintain  
backward compatibility)

  +++ Wishlist
  > These are potential uses for the Lock system that have been  
requested or proposed by others.
-
-* Implement in Wicked
-* Create admin UI to view current locks and manually remove them.
+* Extend other Horde apps (Mnemo, Nag, ???) to use Horde_Lock

  +++ Contact
  > Ben Klang <[email protected]>

--
To unsubscribe, mail: [email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.