Hi,
On Thu, Mar 7, 2013 at 2:05 PM, Michael Dürig mdue...@apache.org wrote:
Yes I'm also a bit worried about this. Couldn't this lead to cascading
undos? And further to violation of other application constraints when data
gets uncommited? I think this is a very slippery slope...
The way I see
Jukka, Marcel,
you saw this problem for SegmentMK which uses branch-merge extensively, but is
this not a problem all distributed MK implementations will run into? After all,
branch-merge is part of the MK API. Unless the MK impl uses pessimistic locking
from the start, of course.
In
Hi,
On Fri, Mar 8, 2013 at 3:32 PM, Michael Dürig mdue...@apache.org wrote:
2) Synchronize SessionDelegete.perform(), which effectively serializes *all*
JCR calls on a single session.
As mentioned earlier, this is what I'd do. A client for which this is
a problem can always open new sessions
On 8.3.13 13:41, Jukka Zitting wrote:
Hi,
On Fri, Mar 8, 2013 at 3:32 PM, Michael Dürig mdue...@apache.org wrote:
2) Synchronize SessionDelegete.perform(), which effectively serializes *all*
JCR calls on a single session.
As mentioned earlier, this is what I'd do. A client for which this
