Description
We should have optional support for clients that assume sessions to always reflect the latest state of the repository.
One way of doing that would be some "auto-refresh" mode that makes the session refresh itself whenever any JCR method call is made. The performance hit for such a mode should be reasonably small as long as the refresh() method can be optimized to a no-op in case the underlying repository hasn't changed.