what questions do you have? All I can think to say right now is
look at Catalyst::Engine::HTTP::Prefork and work from there…
I'm curious if anyone's implemented a zero downtime restart system
(the likes of which FastCGI gives you for free) or if it already
exists somehow. Currently we just
Hi Brad,
* Brad Bowman l...@bereft.net [2009-06-09 10:05]:
Aristotle Pagaltzis wrote:
I like to use ::Engine::HTTP::Prefork coupled with whatever
reverse proxy server strikes one’s fancy (whether it be Squid,
Apache mod_proxy, Varnish, lighttpd, whatever). Additionally I
like to use
On Sat, Jun 20, 2009 at 9:11 AM, Aristotle Pagaltzispagalt...@gmx.de wrote:
Hi Brad,
* Brad Bowman l...@bereft.net [2009-06-09 10:05]:
Aristotle Pagaltzis wrote:
I like to use ::Engine::HTTP::Prefork coupled with whatever
reverse proxy server strikes one’s fancy (whether it be Squid,
Apache
* Matt S Trout dbix-cl...@trout.me.uk [2009-06-08 21:00]:
Shadowcat's clients tend to end up on $webserver + FastCGI
or $proxy + Prefork depending on their requirements.
What sort of requirements does FastCGI cover better in your
experience?
Regards,
--
Aristotle Pagaltzis //
On Mon, Jun 08, 2009 at 11:09:24PM +0200, Aristotle Pagaltzis wrote:
What sort of requirements does FastCGI cover better in your
experience?
I don't know what Matt has in mind, but doing zero-downtime restarts with
FastCGI over a unix socket is pretty easy because of filesystem semantics.
hdp.
* Mark Blackman m.black...@fairfx.com [2009-05-31 22:10]:
However, lightppd+fastcgi with the fastcgi catalyst server is
the usual answer for this requirement. For me, the most
appealing characteristic of this arrangment was merely the
complete decoupling of the front and back ends.
I like to
