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

RE: Loop Detected

From: Clemm, Geoff <gclemm@Rational.Com>
Date: Wed, 15 Mar 2000 16:29:00 -0500
Message-ID: <65B141FB11CCD211825700A0C9D609BC01D4D777@chef.lex.rational.com>
To: w3c-dist-auth@w3.org
I agree with Tim.  Furthermore, I would suggest that the example use
the DAV:urn property (aka DAV:resource-id), since that illustrates the
value of the DAV:urn property (the DAV:display-name is not a reliable way
of identifying a resource).


-----Original Message-----
From: Tim Ellison/OTT/OTI [mailto:Tim_Ellison@oti.com]
Sent: Wednesday, March 15, 2000 3:29 PM
To: w3c-dist-auth@w3.org
Subject: Loop Detected

The example given in section 12.1 of draft-ietf-webdav-binding-protocol-02
of a PROPFIND depth infinity in the presence of a loop implies that the
propstat for the loop detected resource only contains the property names
and not their values (again).
Although I can understand the point of this in the majority of cases, it
does prevent the client from reconstructing the graph of resources since
they cannot determine the destination of the binding.  If the properties
were returned the client could PROPFIND depth infinity on the resource
identifier and reconstruct the graph.

Received on Wednesday, 15 March 2000 16:29:48 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:01:21 UTC