- From: Roy T. Fielding <fielding@gbiv.com>
- Date: Thu, 27 Jan 2005 19:27:19 -0800
- To: Lisa Dusseault <lisa@osafoundation.org>
- Cc: Geoffrey M Clemm <geoffrey.clemm@us.ibm.com>, " webdav" <w3c-dist-auth@w3.org>
On Jan 27, 2005, at 6:31 PM, Lisa Dusseault wrote: > Yes, but as I explained in this email -- > http://lists.w3.org/Archives/Public/w3c-dist-auth/2005JanMar/0065.html > > -- the bindings draft introduces the possibility for client behavior > which could be harmful to interoperability unless the way that ETags > interact with bindings is defined. And has been explained in multiple responses, bindings does not introduce such behavior -- it is present in any implementation that allows such things as Alias configurations -- and there is absolutely nothing that bindings can say about it that isn't already in the definition of etag in RFC 2616. > Since bindings first introduces this possibility, that's our best > choice for a document in which to resolve that potential > interoperability problem. There is no interoperability problem. You are imagining that there might be an interoperability problem if the client developer makes an egregious mistake in assuming the implementation behind the interface defined by HTTP. Quite frankly, that is not our problem. ....Roy
Received on Friday, 28 January 2005 03:27:18 UTC