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

Re: [dav-dev] Depth Infinity Requests]

From: Jim Whitehead <ejw@ics.uci.edu>
Date: Fri, 7 Jul 2000 08:44:39 -0700
To: WebDAV WG <w3c-dist-auth@w3.org>
Message-ID: <NDBBIKLAGLCOPGKGADOJEEINDGAA.ejw@ics.uci.edu>
This is the last message caught in the spam filter yesterday.

- Jim

-----Original Message-----
From: Kevin Dyer [mailto:kevin.dyer@matrixone.com]
Sent: Thursday, July 06, 2000 10:40 AM
To: w3c-dist-auth@w3.org
Subject: [Moderator Action] Re: [dav-dev] Depth Infinity Requests]




> -----Original Message-----
> From: w3c-dist-auth-request@w3.org
> [mailto:w3c-dist-auth-request@w3.org]On Behalf Of Gary Barnett
> Sent: Thursday, July 06, 2000 12:58 PM
> To: WebDAV WG
> Subject: RE: [hwarncke@Adobe.COM: Re: [dav-dev] Depth Infinity Requests]
>
>
> I think that creating a specification that builds in non-deterministic
> behaviour would be a real pain.
>
> I think that the idea of passing a depth value (with perhaps a default
value
> which all servers support) makes sense from a client perspective.
>
But you still need to be able to tell the client that you've asked for too
much
and I'm only going to give you back this amount.  Or you've asked for
something
that I can't generate now.  Maybe the 403 is not the answer, but a new
return
code that actually tells the client what the high water mark is.

I apologize if this is in the latest version, shouldn't the client be able
to
request from the server all of the high and low watermark settings we've
been
talking about as part of a handshake?



Kevin
Received on Friday, 7 July 2000 11:48:45 GMT

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