W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > January to March 2005

Re: Discovering bindings in BIND

From: Geoffrey M Clemm <geoffrey.clemm@us.ibm.com>
Date: Wed, 19 Jan 2005 22:02:50 -0500
To: Julian Reschke <julian.reschke@gmx.de>
Cc: Joe Hildebrand <JHildebrand@jabber.com>, webdav <w3c-dist-auth@w3.org>, w3c-dist-auth-request@w3.org
Message-ID: <OF2A4BA302.6B25DC68-ON85256F8F.000F3CE2-85256F8F.0010BCEE@us.ibm.com>
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


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 
> > 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 
> > (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 
> > 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

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:33 UTC