Author: mduerig
Date: Tue Aug 27 08:13:33 2013
New Revision: 1517760

URL: http://svn.apache.org/r1517760
Log:
OAK-301 Document Oak
update section on session synchronisation to reflect the latest changes done in 
OAK-960

Modified:
    jackrabbit/oak/trunk/oak-doc/src/site/markdown/differences.md

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=1517760&r1=1517759&r2=1517760&view=diff
==============================================================================
--- jackrabbit/oak/trunk/oak-doc/src/site/markdown/differences.md (original)
+++ jackrabbit/oak/trunk/oak-doc/src/site/markdown/differences.md Tue Aug 27 
08:13:33 2013
@@ -50,16 +50,15 @@ This change can cause subtle differences
 relying on one session seeing the other session's changes. Oak requires 
explicit calls to
 `Session.refresh()`in this case.
 
-----------------------------------------------------------------------------------------------------
-
-*Note*: To ease migration to Oak, sessions will currently automatically 
refresh after being idle
-        for more than one second. Sessions being idle from more than one 
minute will log a warning
-        to the log file.
-        This is a transient feature and will most probably be removed in 
future versions of Oak.
-        See [OAK-803](https://issues.apache.org/jira/browse/OAK-803) for 
further details and for
-        how this behaviour can be changed.
-
-----------------------------------------------------------------------------------------------------
+> *Note*: To ease migration to Oak, sessions will currently automatically 
refresh after being
+> idle for more than one second. Sessions being idle for more than one minute 
will log a warning to
+> the log file. Furthermore sessions are automatically synchronised to reflect 
the same state across
+> accesses within a single thread. That is, an older session will see the 
changes done through a
+> newer session given both sessions are accessed from within the same thread.
+>
+> Automatic session synchronisation is a transient feature and will most 
probably be removed in
+> future versions of Oak. See 
[OAK-803](https://issues.apache.org/jira/browse/OAK-803) for further
+> details.
 
 On Oak `Item.refresh()` is deprecated and will always cause an 
`Session.refresh()`. The former call
 will result in a warning written to the log in order to facilitate locating 
trouble spots.


Reply via email to