On Fri, 2006-02-17 at 02:26 -0800, Justin Erenkrantz wrote:
> As of r18500, we now open 4 connections to the server in order to do
> the checkout. Part of the reason for this is that as we parse the
> REPORT response, we can start to fetch the actual content. While we
> can keep it to one connection (and have done so until just now), we'll
> essentially be blocked for the length of the REPORT response
Aren't two connections good enough for maximum efficiency, then? If
you're pipelining, I don't see why three connections for the GETs is
better than one.
I'm actually unsure why you need more than one connection total. You
can be sending GETs to the server as you're parsing the REPORT response,
then start handling GET responses as soon as the REPORT response is
done. The server should be sending data full-time, with only one
round-trip delay at the beginning to send off the first GET request.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Feb 17 15:48:55 2006