- From: Greg Stein <gstein@lyra.org>
- Date: Sat, 10 Feb 2001 02:02:09 -0800
- To: ietf-dav-versioning@w3.org
And also given what Geoff said, it is entirely reasonable for an OPTIONS on /foo to return an entirely different result than OPTIONS on /bar. Thus, if the two URLs are served by different servers, or they are simply configured differently, they can return different workspace-collection-set values. IMO, it is still quite ridiculous to do some discovery through OPTIONS, and other discovery through PROPFIND. OPTIONS is defined to be per-resource (if you want general server options, the use "*" for the Request-URI). Arbitrarily classifying a subset of information as "more useful in a Depth: context, so we'll put it into PROPFIND" is just that: arbitrary. In layman's terms, that is a synonym for "bogus". :-) Cheers, -g On Sat, Feb 10, 2001 at 12:11:48AM -0500, Clemm, Geoff wrote: > The DAV:workspace-collection set is usually the same for a > whole server, so just like the DAV header, there is no need > to query it for more than one resource on a given server. > > In contrast, the supported methods and live properties vary > from resource to resource, and therefore are more appropriately > marshalled as a property so that it can easily be retrieved > in a depth fashion with the other information about that resource. > > Cheers, > Geoff > > -----Original Message----- > From: James J. Hunt [mailto:jjh@allerton.de] > Sent: Monday, February 05, 2001 1:15 PM > To: Geoffrey M. Clemm > Cc: ietf-dav-versioning@w3.org > Subject: Re: Option abuse > > > "Geoffrey M. Clemm" wrote: > > > > > It really doesn't matter whether we marshall this as an OPTIONS call > > or as a PROPFIND for a property. This used to be marshalled as a > > property but a reviewer pointed out that this information seemed more > > like an option than a property. > > > > Can you give some motivation for switching this back to being a property? > > > > Cheers, > > Geoff > > Dear Geoff, > > My understanding of an option is "does the server support x". Properties > associate values to keys for a given resource. Let us take > DAV:workspace-collection-set. Especially when you say that the http > namespace > can be spread over several servers, the question I ask with this tag is not > do > you support workspaces, rather for a given versionable workspace, where can > I > create a workspace for it? In other words, I am asking what is the > workspace > area associated with this resource. That seems to me to be a property of > that > resource, because every resource could answer it differently. > > Sincerely, > James -- Greg Stein, http://www.lyra.org/
Received on Saturday, 10 February 2001 05:00:33 UTC