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

RE: [hwarncke@Adobe.COM: Re: [dav-dev] Depth Infinity Requests]

From: Jim Whitehead <ejw@ics.uci.edu>
Date: Fri, 7 Jul 2000 08:43:53 -0700
To: WebDAV WG <w3c-dist-auth@w3.org>
Another message caught yesterday by the spam filter. :-(

- Jim

-----Original Message-----
From: Kevin Dyer [mailto:kevin.dyer@matrixone.com]
Sent: Thursday, July 06, 2000 10:30 AM
To: Kevin Wiggen; WebDAV WG
Subject: [Moderator Action] RE: [hwarncke@Adobe.COM: 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 Kevin Wiggen
> Sent: Thursday, July 06, 2000 12:28 PM
> To: Hartmut.Warncke@Adobe.COM; WebDAV WG
> Subject: RE: [hwarncke@Adobe.COM: Re: [dav-dev] Depth Infinity Requests]
> I believe we should follow the DASL spec on this one.  Dasl allows a
> to send a 507 if the query produced more results than the server is
> to transmit.  Partial Results have been transmitted.

| From Tim Ellison
| The server should be free to refuse depth requests (>1<g>) that it decides
| are too expensive.  Of course, that does not preclude the spec from
| allowing the header value to be 0 .. n or infinity, but it does further
| complicate the client that has to deal with refusals and 'do the work'.

Then the server can respond to an infinite request with either a 403, if the
admin decides to be frugal with server resources, or a 507 and send up to
high water mark of depth.  It leaves more wiggle room but it looks like the
best solution.

> This is the implementation on the Xythos Storage Server for both SEARCH
> Kevin

Received on Friday, 7 July 2000 11:48:00 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:01:22 UTC