Greg Stein wrote:
> just fyi, Phillip: Justin is *very* aware of this, and many of the
> other details you mention in your email. He is a long-time contributor
> to Apache, and one of the design goals of serf is to take advantage of
> pipelining (which nearly all HTTP clients do *NOT* do). Point is:
> rejigger your emails to assume Justin knows HTTP, and ask why he is
> making certain choices, instead of teaching him about HTTP :-)
>
Cool, thanks for the heads up. I see that now that I'm reading the
other messages in this thread. I too hope to see a day when the clients
utilize pipelining and the server takes advantage of zero copy async IO
with a number of threads/processes significantly less than the number of
clients.
> The server closes it down periodically. Thus, the client needs to
> reopen it. To keep traffic flowing, you want to have another
> connection ready for immediate use while you go thru the TCP setup to
> reopen the closed connection.
>
Right... you want to open the next connection and prime it's pipeline
just before the first connection is closed. It sounded like ra_serf
just opens 4 connections and gets them all going in parallel. Maybe I
just misunderstood?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Feb 17 18:26:28 2006