Re: Future MPM Support?

Yes, http/2 is our primary concern right now.  At the moment, we've made 
the business decision to stay on mod_perl rather than migrate to another 
platform and gain http/2 benefits, but for how long can we maintain that 
decision?  I'm honestly not sure.

Now, we significantly under-utilize mod_perl, mostly doing CGI registry 
/ code caching.  Hey, if it was good 15 years ago, it's good today! :)  
But that does mean that there are potentially other options for us to 
explore, as we're not married to all the bells and whistles that 
mod_perl provides.

On 8/4/2018 5:47 AM, Paul Silevitch wrote:
> Also issues with http/2 since it is not supported by prefork mpm anymore.
>
> On Wed, Aug 1, 2018 at 12:44 PM, John Dunlap <[email protected] 
> <mailto:[email protected]>> wrote:
>
>     The biggest deficiency of mod_perl, at the moment, is that it
>     cannot provide web sockets. In today's world, that's a huge problem.
>
>     On Wed, Aug 1, 2018 at 11:30 AM, Robert Smith
>     <[email protected] <mailto:[email protected]>> wrote:
>
>         Who in the world would want to abandon mod_perl?
>
>         What is this world coming to?
>
>         -Robert
>
>         > On Jul 30, 2018, at 5:44 PM, André Warnier (tomcat)
>         <[email protected] <mailto:[email protected]>> wrote:
>         >
>         > On 30.07.2018 03:51, Paul B. Henson wrote:
>         >> On Sun, Jul 29, 2018 at 04:18:54PM -0400, Paul Silevitch wrote:
>         >>> Like Dr. James Smith, I'm hooking into multiple handlers
>         and using filters.
>         >>
>         >> Yep, me too; Plack is really not a feature equivilent
>         replacement for
>         >> mod_perl :(.
>         >>
>         > +1.
>         > Plack and other frameworks (TT2, Moose, Catalyst, etc.)
>         cover the web application side, at different levels and in
>         different ways.
>         > But there is (to my knowledge) no equivalent for mod_perl's
>         ability to interact deeply with the Apache internal Request
>         processing logic.
>         > In that respect, comparing mod_perl to Plack etc is like
>         comparing apples to pears : not very relevant.
>         > Considering that, for better or worse, Perl as a programming
>         language does not seem to be really attractive to the current
>         generation of software developers anymore, I would not really
>         mind if some tool equivalent to mod_perl was developed using
>         whichever other scripting language is currently more in
>         fashion (javascript ? python ? ..), but it really seems a pity
>         to "slowly abandon" mod_perl without providing some tool of
>         equivalent power in terms of deep interaction with Apache httpd.
>         >
>         >
>         >
>
>
>
>
>     -- 
>     John Dunlap
>     /CTO | Lariat/
>     /
>     /
>     /*Direct:*/
>     /[email protected] <mailto:[email protected]>/
>     /
>     *Customer Service:*/
>     877.268.6667
>     [email protected] <mailto:[email protected]>
>
>