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 ::Plugin::Static::Simple, sending proper Expires
headers so that the reverse proxy will keep those cached files
around forever.
That takes decoupling to its logical conclusion: the application
server is standalone and works completely independently from the
internet-facing server. You can fire requests at it like you
would at any webserver. You can use the same engine during
development and in production. There are more advantages, but
I forget.
It’s all very, very nice.
I'd like to know more about this.
(It almost sounds to good to be true...)
Brad
--
An affected laugh shows lack of self-respect in a man and lewdness in a woman.
-- Hagakure http://bereft.net/hagakure/
_______________________________________________
List: Catalyst@lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/