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 Wed, 06 Feb 2008 15:36:14 GMT
hi julian

> this issue made me think that we may be missing something in the SPI...
> 
> So, is an SPI implementation allowed to internally cache things (for 
> instance, with the SessionInfo implementation)? I would assume so (but 
> maybe I'm wrong).

> If it is allowed to do that, shouldn't a Session.refresh() call be 
> reflected in some SPI call, so that the SPI implementation can 
> invalidate caches as well?

that sounds strange to me. if the SPI does some kind of caching
it should rather communicate with the implementation below in
order to update/refresh the cache.

see however JCR-1012 for potential improvement of
Session.refresh()... that could result in some extension
of the SPI. but at first glance propagating the 'refresh'
to the SPI however looks wrong to me.

am i missing something?
angela


> BR, Julian
> 


Mime
View raw message