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

To use an analogy, I use the UNIX "find" command a lot to find
files. If it's used at the root of the file system, it includes
all the remotely mounted file systems too. Even just searching
the local files system takes quite a while. But when that's what 
I want to do, that's what I need to get done. If I decide it's 
taking too long, I simply kill it.

So, is there a way to kill a request that's taking too long?
If so, that helps quite a bit. A general mechanism for canceling 
operations addresses the problem for all long running operations.
You want a general solution, not a special solution for each
long running operation.

Alan Babich

-----Original Message-----
From: Jim Davis [mailto:jrd3@alum.mit.edu]
Sent: Thursday, July 06, 2000 1:09 PM
To: Greg Stein; w3c-dist-auth@w3.org
Subject: Re: [hwarncke@Adobe.COM: Re: [dav-dev] Depth Infinity Requests]


At 07:15 AM 7/6/00 -0700, Greg Stein wrote:
>What is the general consensus on PROPFIND with Depth: infinity? I quoted a
>couple messages below that tend to favor disallowing them. I got that
>impression from some other comments on this list, but couldn't find
specific
>references.
>
>For clarity: can prople give opinions on simply disabling PROPFIND
infinity?

I oppose disabling infinity.  it is useful (as other emails have shown).

I agree to adding a principled way to refuse a request that's too expensive.

Received on Thursday, 6 July 2000 20:44:56 UTC