jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Angela Schreiber <anch...@day.com>
Subject Re: SPI caching, was: [jira] Resolved: (JCR-1361) Lock test assumes that changes in one session are immediately visible in different session
Date Thu, 07 Feb 2008 11:41:39 GMT
Julian Reschke wrote:

> If the JCR client does call "refresh()", we really should pass that 
> information to SPI, either by a new method (which could be more 
> elaborate than just refresh() as mentioned by Angela), or just discard 
> the SessionInfo and get a fresh one.

i wouldn't state, that we pass the refresh to the SPI.

but it would definitely make sense to me, to have the
ability to let the client find out, whether there are
changes at all. given the assumption that most of
the time nothing changes (that's what i always get
told) that would save the client quite some unnecessary
invalidation and communication with the spi.

if a SPI impl isn't able the provide that info, we have
the same situation as we have now. legal as well.

i wouldn't expect an SPI impl to hold caches either.
but if you want to use that "anychanges?" as hint for
whatever stuff inside the SPI... i wouldn't mind...

am i missing anything fundamental?

View raw message