[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: DAV lock-token decisions. (please read)

From: Justin Erenkrantz <justin_at_erenkrantz.com>
Date: 2005-01-19 19:57:12 CET

--On Wednesday, January 19, 2005 12:13 PM -0600 Ben Collins-Sussman
<sussman@collab.net> wrote:

> Mike Pilato has an idea, though I'm not sure how I feel about it. He
> thinks that if the final MERGE request gets an error regarding header
> limits, it can re-try the commit using a new custom REPORT request.
> Kinda icky.
> Feelings? Should I just bite the bullet and implement a new custom
> REPORT? I wonder if ra_dav shouldn't just use the new REPORT-type
> whenever lock-tokens are present.

For the record, I'm against a new custom REPORT at this time. I'm of the
idea that we should see if this actually becomes a real issue. We can
determine this once we release 1.2.0-beta's and get real-world feedback.
My rough back-of-the-envelope estimate is that we can do about 5,000 locks
in a single HTTP request (~70 per single If header and about 80 If headers).

If you have over 5k locks, then I don't think it's unreasonable for us to
say that you need to bump up your header limit in httpd.conf... -- justin

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jan 19 19:58:30 2005

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.