W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > July to September 2005

Re: BIND and live property value consistency

From: Lisa Dusseault <lisa@osafoundation.org>
Date: Wed, 06 Jul 2005 09:10:17 -0700
To: "Julian Reschke" <julian.reschke@gmx.de>, "Brian Korver" <briank@briank.com>
Cc: webdav <w3c-dist-auth@w3.org>
Message-ID: <op.sth1vfmreochem@lisa.local>

Sure; how about this?  The general requirement and specific requirement  
don't have to be in the same place in the document so I've called them out  
separately.

General requirement: "All live properties defined in RFC2518 MUST have the  
same value across all bindings to the same resource. "

Specific: "The DAV:getlastmodified property MUST change when the  
underlying resource body is altered.  The property value MUST NOT change  
when a new binding to the resource is created or when a binding to the  
resource is removed.  If a collection has a DAV:getlastmodified property  
then its value SHOULD change whenever its set of bindings changes  
(including new bindings, removed bindings or bindings where the name or  
target changes).  "

I'm sure this could use some tweaking, but this is the general idea.  With  
these requirements the property continues to behave the way that it would  
before bindings, tied to the HTTP header and all.  A client that is  
unaware that bindings exist would not find any unusual behavior as a  
result of these requirements -- a PUT would still update the last modified  
stamp, and creation or deletion of a binding elsewhere (an event  
unnoticeable by a client that doesn't support bindings) wouldn't  
surprisingly change the value.

Lisa

On Tue, 05 Jul 2005 17:40:22 -0700, Julian Reschke <julian.reschke@gmx.de>  
wrote:

>
> Let's start with the hardest one. As far as I understand, Lisa wants the  
> BIND spec to put additional constraints on how DAV:getlastmodified, i.e.  
> the HTTP lastmodified response header, behaves. Right now, I have  
> absolutely no idea what kind of constraint this could be.
>
> Please make a proposal for actual spec text that the WG can consider.
>
> Best regards,
>
> Julian
>



-- 
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
Received on Wednesday, 6 July 2005 16:10:31 GMT

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