RE: Attributes in Prelim DAV Spec

We need to be able to lock, copy, move, redirect, delete, destroy, etc.
attributes just as we can do the same with any other resource. Your
syntax does not allow this.
	Yaron

>-----Original Message-----
>From:	Kenji Takahashi [SMTP:kt@nttlabs.com]
>Sent:	Tuesday, November 12, 1996 1:03 PM
>To:	Larry Masinter
>Cc:	w3c-dist-auth@w3.org
>Subject:	Re: Attributes in Prelim DAV Spec 
>
>Larry,
>
>>Suppose that a versioning-aware server just returns a LINK header, e.g.,
>>   GET http://www.cern.ch/TheBook/chapter2 HTTP/1.1
>>returns headers that include
>>   Link: <http://www.cern.ch/meta-repository/TheBook/chapter2>;
>>rel="MetaData"
>>
>>and then the client will know that it can do GETs against 
>>the linked URL to get and modify the attributes of the included
>>URL. 
>
>This is dangerous because attributes or something may change during two
>transactions.  For example, the content may be changed after the GET of
>the content and before the GET of the attributes.  This results in 
>the inconsistency between the contents and attributes.  So, I thingk
>the content and its attributes should be gotten in one transaction.
>
>How about the following (we are implementing this now).   The attributes 
>are sent as HTTP headers with the content with options.  To specify options, 
>I would like to propose "request-attributes" header for GET.  If this header 
>is not included in the GET request, attributes are not sent.  For example, 
>if you would like to get the "author" and "lock-state" attributes:
>
>GET http://foo.bar.content
>request-attributes: author,lock-state, etc... 
>
>If you need all the attributes:
>
>GET http://foo.bar.content
>request-attributes: *
>
>If you need only the attributes.
>HEAD http://foo.bar.content
>request-attributes: *
>
>Also I would like to propose something like SET_ATTR to set 
>attributes.  Good symmetry, hah?
>  GET  <-> PUT
>  HEAD <-> SET_ATTR
>
>Best regards,
>
>Kenji
>

Received on Tuesday, 12 November 1996 20:19:53 UTC