W3C home > Mailing lists > Public > ietf-dav-versioning@w3.org > July to September 2001

Re: Allow: header and supported methods

From: Tim Ellison <Tim_Ellison@uk.ibm.com>
Date: Tue, 14 Aug 2001 13:26:12 +0100
To: ietf-dav-versioning@w3.org
Message-ID: <OFA7817E2D.C5347208-ON80256AA8.0043B83D@portsmouth.uk.ibm.com>
Ben Evans <ben.evans@parasolsolutions.com> wrote:

> Surely for a server looking after versioned resources,
> asking it "What If?" questions based on its current
> state is a bit useless?

I agree, and I think that is why people were happy enough to say that the
response includes methods that are valid for different states of the same
resource.

> I mean, if I have a checked-out resource, and I don't
> have an exclusive write-lock on the resource, then
> requests to the server such as "If I try and commit,
> will I be able to?" can only be usefully answered by
> the server with: "I don't know, unless you try."

Yes, and there are other examples.  You could have changed the state of the
resource (or DELETEd it for that matter) between me asking for the allowed
methods and then actually issuing it.

> Is there a more subtle issue I'm missing?

Don't think so, other than to say the principal use of the supported-*-sets
is to allow for resource 'classification' which is typically required for
high-level UIs to choose icons, grey-out or enable menu options, and so on.

Regards,
Tim
Received on Tuesday, 14 August 2001 08:26:56 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 13:57:42 GMT