Re: RE: Change to Lock-Token

The lock model we have discussed todate requires that lock tokens
be distributed across the entire network and that lock token validation
be performed before some methods are executed. I don't think that cross
server locks are "FAR FAR FAR" into the future, they are very
close.

-src

>>> Yaron Goland <yarong@microsoft.com> 03/24/97 06:23PM >>>
The problem is that e-tags are opaque and we really need to be able to
put lock tokens into if-match headers. Are we going to be forced to
invent our own "if-match" header for lock tokens or can we extend the
if-match syntax to accept tokens?

My feeling is that lock tokens should be URIs (this also gives the
possibility of having cross server locks on day, FAR FAR FAR into the
future =) and that we should extend the e-tag if headers to accept
tokens instead of just quoted strings.

   Yaron

> -----Original Message-----
> From: Larry Masinter [SMTP:masinter@parc.xerox.com] 
> Sent: Monday, March 24, 1997 10:34 AM
> To: Jim Whitehead
> Cc: w3c-dist-auth@w3.org 
> Subject: Re: Change to Lock-Token
> 
> > 2) Identity.  While a strong entity tag will correspond to the
> resource
> > when a lock is taken out on that resource, as soon as the resource
> is
> > changed its entity tag (strong for sure, weak potentially depending
> on the
> > scope of the change) will also need to change.  If intermediate
> results are
> > saved to the HTTP server before the lock is released, the lock token
> will
> > no longer correspond to the actual entity tag of the resource.
> 
> This is a good argument for why lock tokens shouldn't be used as
> entity
> tags, then.
> 
> --
> http://www.parc.xerox.com 
>

Received on Tuesday, 25 March 1997 13:19:28 UTC