W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > October to December 2002

RE: Interop issue: Proposal for fixing lock token provision

From: Clemm, Geoff <gclemm@rational.com>
Date: Tue, 8 Oct 2002 13:43:52 -0400
Message-ID: <E4F2D33B98DF7E4880884B9F0E6FDEE25ED47A@SUS-MA1IT01>
To: "'Webdav WG'" <w3c-dist-auth@w3c.org>
Perhaps you could explain this with an example?

In particular, whenever you would have a client submit:

New-If-Header: token-1 token-2

I would have that client submit:

If: <lockroot-1> (<token1>) <lockroot-2> (<token-2>)

Other than the minor syntactic swill, and the addition of the
lockroot tag, what is the difference in terms of client effort?
(Semantically of course there is a difference, in that
you cannot submit invalid lock tokens in If, but
that is a separate issue). 

Cheers,
Geoff



-----Original Message-----
From: Lisa Dusseault [mailto:lisa@xythos.com]
Sent: Tuesday, October 08, 2002 12:44 PM
To: 'Clemm, Geoff'; 'Webdav WG'
Subject: RE: Interop issue: Proposal for fixing lock token provision


> Using a different header to submit tokens doesn't make it any easier 
> for a client to decide what tokens to submit in the header.  

Yes it does, which is one of the major reasons client developers have
asked for this to be fixed: it makes it possible for clients to submit a
bunch of lock tokens for the same "area" of the namespace, even if the
client is not sure whether the server would require each lock token.

Since servers are different in how they require lock tokens for various
operations, this allows clients to submit as many lock tokens as they
believe they need, without failing on some servers.

lisa
Received on Tuesday, 8 October 2002 13:44:28 GMT

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