One minor terminological correction. When Julian said "you can't display *all* bindings to a resource", he meant to say "you can't display all paths a resource is mapped to" (you can display all bindings to a resource, since there are only a finite number of them, and they are enumerated by the DAV:parent-set property). Cheers, Geoff Julian wrote on 01/19/2005 12:44:12 PM: > > Joe Hildebrand wrote: > > Assume I'm writing an authoring client, and want to show UI to theuser with > > an enumeration of all of the bindings to a particular resource. Section 2.9 > > In general, you can't display *all* bindings to a resource. There may be > an infinite number (if a parent collection has a bind loop). > > > of BIND says I get the DAV:parent-set property. However, section 3.2 says > > (and the example in 3.2.1 confirms) that not all of the binding paths can be > > returned in that property. > > It returns all bindings (each with a URI to the collection it's in). If > you need to compute all *paths*, you'll need to redo that step > recursively for these collections. > > > Is the idea that the client would walk up the tree looking for other paths > > to this resource? > > Yes, if it needs to. It just has to keep in mind that doing it without > special loop checks may result in an infinite loop. > > Best regards, Julian > > -- > <green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760 >
Received on Thursday, 20 January 2005 03:03:24 UTC