Mojo is good but it is specifically for fast non blocking services. If you are trying to pull up old monolithic applications into the service based world it might take significant rewrite or you use apache/mod_perl :)
On Tue, Aug 4, 2020 at 8:05 PM jbiskofski <jbiskof...@gmail.com> wrote: > Mod Perl is awesome. That said, the cool kids today are all about Plack. > > Google: Dancer, Mojolicious, Catalyst. These allow you to plugin to all > parts of the HTTP protocol, but obviously not to modify apache > configuration. > Excelent, stable, FAST, production ready HTTP server: Starman > Even faster, but not as proven: Twiggy. > > The most common setup would be with an Nginx process in front. > > I had a hard time accepting this was a good configuration because for 20 > years I had thought of webservers as big giant compiled systems (apache), > but apparently you can now create something just as fast in Perl. > > > > On Tue, Aug 4, 2020 at 5:59 PM Mithun Bhattacharya <mit...@gmail.com> > wrote: > >> The question is move off to what ? I don't see alternatives being shared >> which blows an apache+mod_perl setup out of the water. >> >> On Tue, Aug 4, 2020 at 7:56 PM Ruben Safir <ru...@mrbrklyn.com> wrote: >> >>> On Tue, Aug 04, 2020 at 09:48:48PM +0100, Mark Blackman wrote: >>> > >>> > >>> > > On 4 Aug 2020, at 21:41, Mithun Bhattacharya <mit...@gmail.com> >>> wrote: >>> > > >>> > > I am genuinely curious what are these other "well known" means ? >>> > > >>> > > On Tue, Aug 4, 2020 at 3:37 PM Mark Blackman <m...@blackmans.org >>> <mailto:m...@blackmans.org>> wrote: >>> > > >>> > > >>> > > > On 4 Aug 2020, at 17:58, Mithun Bhattacharya <mit...@gmail.com >>> <mailto:mit...@gmail.com>> wrote: >>> > > > >>> > > > mod_perl does have value because it does a more efficient >>> utilization of resources - this is important when fast response time and >>> scalability is important. The complexity is a known problem but it is not a >>> mystery box either - there is enough documentation which explains what has >>> to happen and what could have gone wrong. >>> > > >>> > > mod_perl’s relative efficiency can be achieved by other well-known >>> means. >>> > >>> > That would depend on what you mean by "efficient utilisation of >>> resources”. You can get the same general effect, more simply, by running a >>> high-performing pre-forking Perl web application server and a web server >>> with a simple configuration in front of it ,instead of a complicated >>> Apache+mod_perl installation. >>> > >>> > That also buys you a nice separation of concerns, the web server >>> handles all the complicated host or path rewrites and access control and >>> the Perl app focuses on responding to the, now-sanitised, fully normalized, >>> HTTP requests. >>> > >>> >>> Not really and the separtion is not a concern, it is an asset, the most >>> important one. >>> >>> To get faster, you would need to move off apache. >>> >>> >>> > - Mark >>> > >>> > >>> > >>> >>> -- >>> So many immigrant groups have swept through our town >>> that Brooklyn, like Atlantis, reaches mythological >>> proportions in the mind of the world - RI Safir 1998 >>> http://www.mrbrklyn.com >>> >>> DRM is THEFT - We are the STAKEHOLDERS - RI Safir 2002 >>> http://www.nylxs.com - Leadership Development in Free Software >>> http://www2.mrbrklyn.com/resources - Unpublished Archive >>> http://www.coinhangout.com - coins! >>> http://www.brooklyn-living.com >>> >>> Being so tracked is for FARM ANIMALS and extermination camps, >>> but incompatible with living as a free human being. -RI Safir 2013 >>> >>>
