Daniel Mealha Cabrita - 2010-02-17

--------------------------------------
G'day, I've been using ziproxy quite happily to squeeze some more
bytes over a 3G modem connection.

Browsers <-> Ziproxy-User <-> Local Squid <-> Ziproxy-Link <==3G==>
Ziproxy-Fast <-> Remote Squid <==Ethernet==> Internet

(using JPEG2000 transcoding & HTML optimisations)

One thing I've noticed is the Ziproxy-User will keep downloading
requests (upto the Timeout) even if the Browser has gone to another
page.

Squid has a feature called quick_abort which is let's you define rules
on when to stop downloading content when the client has gone away.

Some sites have fairly relaxed quick_abort rules, the idea being that
if you've started downloading an object you may as well complete it
and throw it in the cache.

However I'm on data-capped plan so my Local Squid has aggressive
quick_abort rules, as I don't want to download content that is not at
least being viewed once by a browser. Also a low-speed modem link (say
GPRS) can be quickly congested when there are lot's of multiple
streams.

Because there are only a handful of users on the local network, I have
halved the number of simultaneous network connections on the browsers
(Firefox config) and this has had a good impact.

But really I'd like to be able to limit the number of simultaneous
Ziproxy-User streams (maybe accept, but block until a slot becomes
available) and/or have it quick_about.
--------------------------------------