article about mod_perlite

2009-01-25 Thread Adam Prime
I'm not sure how many of you are aware of chromatic's previous article about "5 things perl 5 needs right now", or about the mod_perlite project that was spawned by some people from sixapart, but chromatic has published another article that's basically a conversation with Byrne Reese and Aaron Ston

Re: article about mod_perlite

2009-01-25 Thread Byrne Reese
Adam, Thank you so much for posting this to the list. The project needs the help of some of the Perl and Apache Module gurus I hope frequent this list. Aaron posted the source to github, but last I heard github had somehow managed to corrupt the source. So, Aaron should now be working on

Re: article about mod_perlite

2009-01-26 Thread Alvar Freude
Hi, first thank you for mod_perlite and the background informations on it. Some days ago we discussed in #perlde (and perhaps will continue to discuss it on the German Perl Wokshop), that beside the ugly slow CGI performance there is one more major problem with Perl for mainstream web applica

Re: article about mod_perlite

2009-01-26 Thread Perrin Harkins
On Mon, Jan 26, 2009 at 1:03 AM, Adam Prime wrote: > I'm not sure how many of you are aware of chromatic's previous article > about "5 things perl 5 needs right now", or about the mod_perlite > project that was spawned by some people from sixapart, but chromatic has > published another article tha

Re: article about mod_perlite

2009-01-26 Thread Adam Prime
Perrin Harkins wrote: On Mon, Jan 26, 2009 at 1:03 AM, Adam Prime wrote: I'm not sure how many of you are aware of chromatic's previous article about "5 things perl 5 needs right now", or about the mod_perlite project that was spawned by some people from sixapart, but chromatic has published an

Re: article about mod_perlite

2009-01-26 Thread Perrin Harkins
On Mon, Jan 26, 2009 at 1:29 PM, Adam Prime wrote: > In the context of people with uber-cheap virtual webhosting, is changing > MaxRequestsPerChild really an option? No, but frankly, uber-cheap virtual hosting will never support mod_perl or mod_perlite. > FastCGI, to me anyway, has a big barrier

Re: article about mod_perlite

2009-01-26 Thread Michael Ludwig
Perrin Harkins schrieb: On Mon, Jan 26, 2009 at 1:03 AM, Adam Prime wrote: http://broadcast.oreilly.com/2009/01/cgi-is-dead-mod-perlite-is-ali.html We discussed this on PerlMonks. Here's my take on it: http://perlmonks.org/?node_id=738192 To quote: | To get the environment they're trying

Re: article about mod_perlite

2009-01-26 Thread mackenna
IMO the profile below does not indicate that the sky is falling. A survey of "how long have you been using computers?" might show a similar distribution. craig www.animalhead.com On Jan 26, 2009, at 10:29 AM, Adam Prime wrote: How long have you been using mod_perl? Just started

Re: article about mod_perlite

2009-01-26 Thread Michael Peters
macke...@animalhead.com wrote: IMO the profile below does not indicate that the sky is falling. A survey of "how long have you been using computers?" might show a similar distribution. Just because it might have the same distribution doesn't mean it's relevant. I bet a question like "How long

Re: article about mod_perlite

2009-01-26 Thread Perrin Harkins
On Mon, Jan 26, 2009 at 2:26 PM, Michael Ludwig wrote: > I think this is technically incorrect in that it does not match the > Apache/LibPHP execution model (which is what I think they're trying to > emulate), where the Apache/LibPHP process does not exit after serving > only a single request. We

Re: article about mod_perlite

2009-01-26 Thread Michael Ludwig
Perrin Harkins schrieb: On Mon, Jan 26, 2009 at 2:26 PM, Michael Ludwig wrote: I think this is technically incorrect in that it does not match the Apache/LibPHP execution model (which is what I think they're trying to emulate), where the Apache/LibPHP process does not exit after serving only a

Re: article about mod_perlite

2009-01-26 Thread Perrin Harkins
On Mon, Jan 26, 2009 at 4:15 PM, Michael Ludwig wrote: > I may be wrong but I used to think that PerlRun provides just that, a > non-persistent execution environment, just like LibPHP. Memory consumed > by the interpreter is not deallocated in either case. (Unless, of > course, I'm wrong.) It's n

Re: article about mod_perlite

2009-01-26 Thread Michael Ludwig
Perrin Harkins schrieb: On Mon, Jan 26, 2009 at 4:15 PM, Michael Ludwig wrote: I may be wrong but I used to think that PerlRun provides just that, a non-persistent execution environment, just like LibPHP. It's not really possible in perl. PerlRun attempts to fake it by removing anything add