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

Re: DAV is complicated and slow?

From: Joe Orton <joe_at_manyfish.co.uk>
Date: 2005-11-27 11:12:03 CET

On Tue, Nov 22, 2005 at 12:08:40AM -0800, Greg Stein wrote:
> On Mon, Nov 21, 2005 at 06:35:58PM -0600, Ben Collins-Sussman wrote:
> > On 11/21/05, Justin Erenkrantz <justin@erenkrantz.com> wrote:
> > > It probably
> > > *does* work today with httpd 2.2 (as SVN sends the L-M headers on GET).
> >
> > Nope, subversion stopped using GET just before 1.0. The only commands
> > that issue GET are 'svn cat' and 'svn diff/merge'. Checkouts and
> > updates are a huge custom REPORT request.
> >
> > So, if we really want to use pipelining and caching, we'd have to
> > switch back the old-styles of checkouts/updates.
> If we had HTTP pipelining in the client, then hell yeah: we'd use the
> old-style series of GETs and PROPFINDs.

A couple of times over the last few years I've take a few stabs at
supporting async request processing in neon (and hence pipelining); I
never really go the full hog because I'm afraid that you can never use
pipelining by default in any general-purpose application, so it never
really seems worth the effort.

You can't really pipeline over SSL - if you start sending request N + 1
when the server wants to renegotiate after reading request N, you're
stuffed. Buggy proxies break pipelining, and most importantly, buggy
transparent proxies - *which you can't tell are there* - break


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Nov 27 11:12:53 2005

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