RE: [long] Re: I-D ACTION:draft-ietf-webdav-versioning-01.txt

> > > If we defined a collection that contains all revisions of a versioned
> > > resource, where a member of that collection is named by its
> > > revision-id, then it would be within these guidelines (i.e. it would
> > > not be URL-munging) for a client to take the collection URL, extend it
> > > with a revision-id, and use the resulting URL to locate the desired
> > > revision.
> >
> > No, I think that doing so would be an extension of the currently
> > known required URL-munging methods.
> I'm not sure I understand why this would be so.  It seems to me that all
> you've got here is a collection that is defined to contain references to
> revisions; the munging going on is the same munging that happens when you
> ask for a member of a collection.  No?

In DAV, the members of a collection are designated with complete
URLs. If the "revision-ID" is used to construct a relative URL which
is combined with the "version collection" to create the URL of a particular
version, then you wouldn't be doing any new URL munging, since you'd
be doing relative URL calculation. However, you'd want to make sure
that the relative URLs constructed didn't contain "/" or "." or reserved


Received on Thursday, 11 March 1999 16:51:36 UTC