On Jan 19, 2005, at 9:44 AM, Julian Reschke wrote: > > Joe Hildebrand wrote: >> Assume I'm writing an authoring client, and want to show UI to the >> user 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). Don't you mean, 'in general, you can...'? I always assumed that having an infinite number of parents is the exception. > >> 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 > > -brian briank@xythos.comReceived on Wednesday, 19 January 2005 20:12:39 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:44:07 GMT