Agree with this we use AAA handlers - but more importantly output
filters to allow content to be decorated per site (independent of what
generates the content perl/java/php proxied content etc...} and add in a
few useful extra logging features that rely on things like transHandlers
and log & cleanup handlers you just can't quite get these working well
with plack/PSGI.
There is a balance between HTTP/1.1 and HTTP/2.0 that you can strike by
mixing a matching backends dependant on content - I use three apaches on
my machines one using event handler which receives all requests, and
servers some static content and proxies back to either a dev apache or
live apache dependent on what the URL is...
This gives me the best of both worlds....
On 25/01/2019 20:15, Paul B. Henson wrote:
On 1/25/2019 11:00 AM, Michael A. Capone wrote:
I have to add my voice to the growing chorus here.
Me too. Frequently when the topic of mod_perl going stale comes up
somebody jumps in with "That's old stuff, you should be using
PSGI/Plack". Those people simply don't understand the overall utility
of mod_perl beyond simply running a webapp <sigh>. I have
authentication and authorization handlers written in mod_perl, and the
ability to directly access the Apache API allows things that PSGI
simply cannot do.
--
The Wellcome Sanger Institute is operated by Genome Research
Limited, a charity registered in England with number 1021457 and a
company registered in England with number 2742969, whose registered
office is 215 Euston Road, London, NW1 2BE.
