jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alexander Klimetschek <aklim...@day.com>
Subject Re: [jr3] Clustering: Scalable Writes / Asynchronous Change Merging
Date Thu, 21 Oct 2010 14:59:57 GMT
On Tue, Oct 19, 2010 at 23:17, Justin Edelson <justin@justinedelson.com> wrote:
> You'd also need to ensure that a single session.save() which touched
> both "immediately" and "eventually" consistent nodes forces a queue
> flush (or at least a queue flush of changesets which touched the same
> set of eventually consistent nodes). This is possibly the trickiest
> part of the implementation.

Right, didn't think about that. Also, as Thomas pointed out,
observation listeners would not always get notified in the same order,
if conflicting merges happen, but maybe that is ok for extreme cases
(and the application expects that).

Regards,
Alex

-- 
Alexander Klimetschek
alexander.klimetschek@day.com

Mime
View raw message