net-http-persistent version 1.4.1 has been released!
* http://seattlerb.rubyforge.org/net-http-persistent
Persistent connections using Net::HTTP plus a speed fix for 1.8. It's
thread-safe too!
Changes:
### 1.4.1 / 2010-10-13
* Bug Fixes
* Don't finish the connection when we're retrying, reset it. Patch by James Tucker.
Eric Hodel wrote:
net-http-persistent version 1.4.1 has been released!
Nice one, Eric!
Just a quick question: Does this support pipelining?
Meaning where I can fire off a request, and before
waiting for a response, fire off another one, then
read both responses (or auto-fire the second one again
if the server dropped it)?
If it doesn't support pipelining, would that require
an API change, or just an implementation detail?
I've always wondered why browsers didn't make more use
of pipelining, it's a great way to reduce latency.
Clifford Heath.
Bump?
Clifford Heath wrote:
Eric Hodel wrote:
net-http-persistent version 1.4.1 has been released!
Nice one, Eric!
Just a quick question: Does this support pipelining?
Meaning where I can fire off a request, and before
waiting for a response, fire off another one, then
read both responses (or auto-fire the second one again
if the server dropped it)?
If it doesn't support pipelining, would that require
an API change, or just an implementation detail?
I've always wondered why browsers didn't make more use
of pipelining, it's a great way to reduce latency.
If you're looking for multiple concurrent HTTP connections, take a look at
Paul Dix's typhoeus: http://github.com/pauldix/typhoeus
···
On Sat, Oct 16, 2010 at 6:40 PM, Clifford Heath <no@spam.please.net> wrote:
Clifford Heath.
Mike Dalessio wrote:
If you're looking for multiple concurrent HTTP connections, take a look at
Paul Dix's typhoeus: http://github.com/pauldix/typhoeus
Cool project, but not what I mean.
Pipelining means sending more than one HTTP request down the socket
at a time, before reading back the first response. It's a way to
reduce TCP latencies, beyond keep-alive.
Clifford Heath.