Re: Status of ra_serf

On Fri, Feb 17, 2006 at 12:02:52PM -0500, Phillip Susi wrote:
> Justin Erenkrantz wrote:
> >
> >Again, HTTP connections are ideally stateless - so, we can't have a
> >very deep pipeline before the server decides to kill us off.
>
> Most servers these days allow you to issue a number of requests over the
> same connection.

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 :-)

>...
> >If you kept it at one connection, you'd have lengthy delays where
> >there is no network traffic because you're constantly reopening the
> >TCP sockets. This isn't ra_svn which assumes a persistent TCP
> >connection for the lifetime of the RA session. -- justin
>
> You aren't reopening the socket if you keep it open and pipelined, thus
> there are no delays. HTTP/1.1 allows persistent connections.

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.

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org