> First is reverse proxy feature (but I think I can write it to polipo
> and sends you patch),
You should be aware that Polipo is not optimised for that kind of
usage. The very least is to tune Polipo differently from the default
configuration, notably increase serverSlots to a very large value (I'd
set it to twice the number of clients that you expect to be serving
simultaneously).
I may be wrong, but my gut feeling, you'd be better off with a proxy
optimised for that kind of usage. A reverse proxy usually runs on the
same LAN as the server, hence it does not need to optimise the
proxy-server link, it should just open as many connections as needed
to the server. All the complexity due to pipelining is useless in
that case.
Note the ``I may be wrong''. I used to believe that Polipo is
unsuitable for large numbers of clients, but after carefully reviewing
the code, I found out that it turned out to be perfectly suitable for
such usage after a wee bit of tuning. I hope the same is true of
reverse operation.
> other thing i 2GB limit for disk cache.
The 2GB limit is not for the on-disk cache -- it's for the internal
data structures of Polipo. Lifting it would require a moderate amount
of work. Definitely doable in one afternoon, though.
Juliusz
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Polipo-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/polipo-users
