W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > January to March 2000

Re: 423 Locked

From: Geoffrey M. Clemm <geoffrey.clemm@rational.com>
Date: Thu, 3 Feb 2000 08:44:41 -0500
Message-Id: <10002031344.AA02297@tantalum>
To: w3c-dist-auth@w3.org

   From: "Rickard Falk" <rickard.falk@excosoft.se>

   Maybe the 423 Locked response should contain a XML body with the
   lockdiscovery property. Then the client doesn't need to do a second request
   to the server, and there will not be a time gap.

There are many would would agree that an XML body with detailed information
about the cause of the error would be a good thing (Yaron, for sure).

In this particular case, the overhead of an extra PROPFIND request
and the time gap probably don't matter much.

Cheers,
Geoff

   > -----Original Message-----
   > From: w3c-dist-auth-request@w3.org
   > [mailto:w3c-dist-auth-request@w3.org]On Behalf Of Kevin Wiggen
   > Sent: den 3 februari 2000 10:03
   > To: Rickard Falk; w3c-dist-auth@w3.org
   > Subject: RE: 423 Locked
   >
   >
   >
   > If you do a Propfind against the resource looking for the lockdiscovery
   > property, the resource should return an Owner and Timeout to the
   > client (if
   > permissions allow).
   >
   > Unfortunately the Owner tag is left undefined, and I am sure each
   > implementation has its own sets of values.
   >
   > Kevin
   >
   >
Received on Thursday, 3 February 2000 08:44:44 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:43:53 GMT