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 16:42:00 GMT
David Rauschenbach wrote:
> Distraction:
> WebDAV notation is better for examples (nodes/collections end with slashes, items don't):
> a/
>   b/
>   c/
>   p1
>   p2
> d/
> Back to the discussion: also worth mentioning is why a requested-depth argument is missing
from getItemInfos. It's just a little strange for the server to choose what to do, or to have
a pre-configured nodetype-specific batch strategy configured there, when the client is where
it's at, where it's known what's to be requested. Particularly if your front end is a WebDAV
query, which you're going to run through SPI to some WebDAV or other back-end. No matter what
the back-end is, you want to know the kinds of things you'd know if you were a WebDAV servlet,
including not only ItemId, but also depth, and named property lists, or allprops.

Maybe there is something to learn from PROPFIND, after all -- not only 
the distinction between depth 0 and 1, but also the ability to specify 
in advance what properties (== child items) to return.

BR, Julian

View raw message