Sounds like mod_perl would benefit from using some CI tools. Looks like ASF
provides some via https://ci.apache.org/?
David Cook
Software Engineer
Prosentient Systems
Suite 7.03
6a Glen St
Milsons Point NSW 2061
Australia
Office: 02 9212 0899
Online: 02 8005 0595
-Original Message-
Fro
I am not interested in performing those duties but could you clarify how many
active PMC members there are currently? It looks like the list at
https://perl.apache.org/about/pmc.html is over 7 years out of date. It’s
unclear how up-to-date the list at
https://projects.apache.org/committee.html?
Hi Wesley,
I don't know all the ins and outs of Starman. I do know that Starman is a
preforking web server, which uses Net::Server::PreFork under the hood. You
configure the number of preforked workers to correspond with your CPU and
memory limits for that server.
As per the Starman documenta
That's interesting. After re-reading your earlier email, I think that I
misunderstood what you were saying.
Since this is a mod_perl listserv, I imagine that the advice will always be to
use mod_perl rather than starman?
Personally, I'd say either option would be fine. In my experience, the ke
As Mithun suggested, it's going to be slow regardless of which web server
option you choose.
It depends on your application, but if it's a user-facing web application, one
way would be to have your client application make an API call to your backend,
the backend enqueues the job in the queue,
I don't really see the utility of this thread, since these are just circular
arguments based primarily on opinion, and no one is going to convince
someone else that their opinion is wrong.
That said, I'll just point out one thing about the earlier comment "How many
platforms can survive 30 years.
