RE: collection with ordered members

GET is entirely unaffected by a WRITE lock, other locks that may be
introduced in the future, such as READ locks, may have something else to
say on the matter.
	Yaron

> -----Original Message-----
> From:	Jim Davis [SMTP:jdavis@parc.xerox.com]
> Sent:	Wednesday, October 29, 1997 12:04 PM
> To:	howard.s.modell@boeing.com; w3c-dist-auth@w3.org
> Subject:	re: collection with ordered members
> 
> At 09:15 AM 10/29/97 PDT, howard.s.modell@boeing.com wrote:
> >I have what I hope is a set of simple questions.
> >
> >Given: a typical webpage with text and inline graphics.
> >
> > Is it "a compound document" by default or must it be declared as
> such??
> 
> I don't think DAV has any concept of "compound document".  There is
> nothing
> to declare.   You might store the page and its graphics in a
> collection,
> but that says nothing about the relationship amongst the pieces.  And
> it
> has nothing to do with the topic of whether collections might have an
> optional order.
> 
> As for your other questions, I am no expert but here's my answers.  If
> I am
> wrong someone will correct me.
> 
> >	a. suppose I want to edit/replace one of the graphics.  Under
> >	    the WEBDAV protocol, do I request/lock just the graphic?
> 
> Yes.  No need to lock the others.
> 
> >	    a1.  If yes, does this also request/lock the document
> containing it?
> 
> No.  If you lock a member, the other members remain unlocked.
> 
> >	    a2. If no, what happens when someone requests the enclosing
> doc?
> 
> Requests, as in GET?  The spec says that GET is entirely unaffected by
> LOCK.  This should answer the remaining questions as well.
> 
> >	b. suppose the graphic in question is referenced by more than
> one
> >		document (like a background, or "line" glyph).  
> 
> >	    b1. Does my having "checked it out" affect requests to any
> or all
> >		 of the documents which reference it?

Received on Wednesday, 29 October 1997 17:55:37 UTC