Thanks to everyone for the tips. I ended up with a httpd reverse proxy
in front of my mod_perl servers. Squid was a resource hog, and overkill
since I don't need caching.
Putting apache in front also allowed me to serve static docs, SSL, and
proxy all in one place, with mod_perl off by itself i
On 4 Aug 2004, at 00:48, Larry Leszczynski wrote:
On Tue, 3 Aug 2004, Philippe M. Chiasson wrote:
I've had lots of success with a light reverse proxy (httpd or squid)
in
front of my mod_perl servers. I would recommend it, as it's simpler
than
2 completely separate servers for dynamic content and
On Tue, 3 Aug 2004, Philippe M. Chiasson wrote:
> I've had lots of success with a light reverse proxy (httpd or squid) in
> front of my mod_perl servers. I would recommend it, as it's simpler than
> 2 completely separate servers for dynamic content and static stuff.
>
> I like squid for this, as
Nathan L. Kugland wrote:
Hi All,
I'm curious as to whether anyone has experience running separate image
servers in low-traffic environments. Is it worth it? Would I be better
off spending time setting up a proxy server? My goal is to minimize the
latency for a small number of concurrent users.
Hi All,
I'm curious as to whether anyone has experience running separate image
servers in low-traffic environments. Is it worth it? Would I be better
off spending time setting up a proxy server? My goal is to minimize the
latency for a small number of concurrent users.
Cheers,
Nathan
--
Nathan
