W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > April to June 2006

Re: Bug 143 (lock refresh), was: WGLC of draft-ietf-webdav-rfc2518bis-14.txt

From: Julian Reschke <julian.reschke@gmx.de>
Date: Fri, 12 May 2006 14:40:45 +0200
Message-ID: <4464824D.2050705@gmx.de>
To: Jason Crawford <nn683849@smallcue.com>
CC: WebDav <w3c-dist-auth@w3.org>

Jason Crawford wrote:
> 
> On Friday, 05/12/2006 at 02:04 ZE2, Julian Reschke 
> <nnjulian.reschke@gmx.de> wrote:
>  > Lisa Dusseault wrote:
>  > > WG on Feb 20 which way we should go on this, and nobody answered.
>  >
>  > That's correct, and that makes me really worry about the amount of
>  > review this is getting. Again, this is an incompatible change both to
>  > clients and servers,
> 
> Is it incompatible?  Clients can use both approaches/headers at once and
> the server can respect which ever.  If in doubt it can respect the newer
> spec since the client has demonstrated knowledge of that.  Right?

Well, no.

First of all, clients can not rely on the fact that setting both headers 
will work. There may be existing servers that choke upon Lock-Token 
request headers for LOCK.

Servers need to respect both, because that's what RFC2518bis says.

This seems to be a lot of changes both client-side and server-side for 
an extremely small gain in protocol beauty. In particular if servers are 
required to support the old syntax more or less infinitely (or did I 
miss an announcement that WebDAV support in MS Office is going to be 
upgraded???).

Anyway: I'd still be interested in *any* implementor saying "yes, this 
is an improvement that we'll going to implement".

Best regards, Julian
Received on Friday, 12 May 2006 12:43:12 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:44:14 GMT