jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marcel Reutegger <marcel.reuteg...@gmx.net>
Subject Re: jackrabbit & clustering
Date Wed, 03 May 2006 13:20:43 GMT
Giota Karadimitriou wrote:
> Thanks for the answers Marcel. One extra question: since shared item
> state manager is entirely responsible for controlling integrity; is
> there a way to check (by querying somehow the database) whether an item
> state is up to date and if not to just reload it from the database.
> Couldn't this ideally work for cluster since everything in our
> application is being saved in a common database? (Of course performance
> would go down with all these db calls but cache would become valid)

well, in theory you could retrieve the item state again from the 
persistence manager and compare the modification count with the item 
state that you already have. if it is the same you know its up-to-date. 
but that may change at any given point in time. imo you need some sort 
of distributed locking to be sure that you only work on up-to-date item 
states.

regards
  marcel

Mime
View raw message