jackrabbit-oak-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ju...@apache.org
Subject svn commit: r1564524 - /jackrabbit/oak/trunk/oak-doc/src/site/markdown/differences.md
Date Tue, 04 Feb 2014 22:12:54 GMT
Author: jukka
Date: Tue Feb  4 22:12:53 2014
New Revision: 1564524

URL: http://svn.apache.org/r1564524
OAK-150: Basic JCR LockManager support

Document the "fuzzy locking" strategy used by Oak


Modified: jackrabbit/oak/trunk/oak-doc/src/site/markdown/differences.md
URL: http://svn.apache.org/viewvc/jackrabbit/oak/trunk/oak-doc/src/site/markdown/differences.md?rev=1564524&r1=1564523&r2=1564524&view=diff
--- jackrabbit/oak/trunk/oak-doc/src/site/markdown/differences.md (original)
+++ jackrabbit/oak/trunk/oak-doc/src/site/markdown/differences.md Tue Feb  4 22:12:53 2014
@@ -177,6 +177,22 @@ bytes in the stream, or that the return 
 stream. Neither assumption is correctly based on the `InputStream` API
 contract, so such client code needs to be fixed to avoid problems with Oak.
+Oak does not support the strict locking semantics of Jackrabbit 2.x. Instead
+a "fuzzy locking" approach is used with lock information stored as normal
+content changes. If a `mix:lockable` node is marked as holding a lock, then
+the code treats it as locked, regardless of what other concurrent sessions
+that might see different versions of the node see or do. Similarly a lock token
+is simply the path of the locked node.
+This fuzzy locking should not be used or relied as a tool for synchronizing
+the actions of two clients that are expected to access the repository within
+a few seconds of each other. Instead this feature is mostly useful as a higher
+level tool, for example a human author could use a lock to mark a document as
+locked for a few hours or days during which other users will not be able to
+modify the document.
 Same name siblings

View raw message