Re: Pipelining

Juliusz Chroboczek <[email protected]>
Newsgroups gmane.comp.web.polipo.user
Message-ID <[email protected]>
> Well, I have a huge latency because of too much users, so that's kind
> of what I need.

You're sufferring from buffer bloat.  Putting the right AQM on your
router will help way more than any application-level hacks.

  http://en.wikipedia.org/wiki/Active_Queue_Management

>> That's what Polipo does by default if the client only speaks /1.0.

> Is that "legal" ? I mean, does the RFC says so, or is it some
> Polipo-specific behavior ?

RFC 2616, Section 3.1:

   caching proxies MUST, gateways MAY, and tunnels MUST NOT upgrade the
   request to the highest version they support. The proxy/gateway's
   response to that request MUST be in the same major version as the
   request.

Polipo is a caching proxy.

> (More seriously, I thought about the in-browser google-talk, which is 
> transmited using a single chunked connection).

Oh yuck.

There's no support in HTTP for multiplexing, so a persistent connection
will use up a server-side slot for the length of its duration.

-- Juliusz

------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security 
threats, fraudulent activity, and more. Splunk takes this data and makes 
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.