jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Julian Reschke <julian.resc...@gmx.de>
Subject Re: SPI caching, was: [jira] Resolved: (JCR-1361) Lock test assumes that changes in one session are immediately visible in different session
Date Fri, 08 Feb 2008 13:10:13 GMT
Marcel Reutegger wrote:
> David Rauschenbach wrote:
>> My main problem with SPI is that if I return depth=1 results from
>> getItemInfos (a NodeInfo for each subfolder), JCR2SPI ends up 
>> subsequently
>> calling getChildInfos anyway, to find out what ALL the children are,
>> regardless of the fact that I just returned what all the children are 
>> in my
>> GetItemInfos response.
> this is because jackrabbit-jcr2spi did not have a cache. angela recently 
> committed the changes discussed in JCR-1011. this introduces a cache and 
> should avoid the calls for the children if they were delivered in a 
> previous call.

How would JCR2SPI that *all* children have been returned? And how should 
the SPI implementation know that somebody *wants* to retrieve all children?

> ...

BR, Julian

View raw message