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: 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 12:41:15 GMT
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.

> It would also not hurt for depth=0 results to be able to return the
> equivalent of IMAP's \HasChildren flag. Because in that case, getItemInfos
> could return depth=0 results, and then in the case where there are no
> children, JCR2SPI could avoid the unnecessary getChildInfos when there are no
> results.

we already considered this, see: JCR-1239


View raw message