Re: polipo, ziproxy

> The upstream ziproxy converts images to jpeg2000, which is much more
> space efficient for the same quality, but Firefox doesn't seem to like
> jpeg2000.

Ah, I see.

If the claims about JPEG 2000 are true, then you should file a bug
against Firefox.  (I've got no opinion myself, but Wikipedia claims that
"While there is a modest increase in compression performance of JPEG
2000 compared to JPEG, the main advantage offered by JPEG 2000 is the
significant flexibility of the codestream.")

> Am I right, that persistent connections without pipelining may even
> increase latency, since requests are serialized in a single TCP
> connection,

Not quite.

There's nothing preventing you from using multiple persistent
connections.  Polipo uses 2 with HTTP/1.1 servers, and 4 with HTTP/1.0
servers (which don't support pipelining).

> certainly if you're talking to your own proxy, you should be able to
> set the browser to open a whole load of parallel connections without
> getting booted off for abusing the server.

I don't care about the servers -- admins using Apache get what they
deserve.  (Hint: use lighttpd, your problems with large numbers of
clients will disapper.)  Please read the Polipo manual to find out why
persistent connections are desirable.

You're right to note that there's a number of difficult tradeoffs here.

> Essentially everything is working quite nicely as it is, so thanks very
> much for all your work on polipo, but I would like to try and get it
> running the best possible way.

Thanks for the kind words.

                                        Juliusz

------------------------------------------------------------------------------
This SF.net email is sponsored by 

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev