[MTOS-dev] Background Task Change

[Byrne Reese]

Mod Perl is persistent, where as Mod-Perlite is not. Which means:

* it is not as prone to memory leaks
* it is easier to configure and setup


On 2/13/08 6:28 AM, "David Scott" <ds94103 at earthlink.net> wrote:

> How is this different from Apache 2 / mod_perl2 with Worker MPM?
> 
> d
> 
> Byrne Reese wrote:
>> Did you guys ever hear of the project I started at Six Apart called
>> mod_perlite? The concept was to model a stateless apache module for process
>> perl scripts based upon mod_php.
>> 
>> In this implementation, the Perl interpreter would be loaded into Apache's
>> memory space and would be spawned into threads by apache itself. No forking
>> required. 
>> 
>> The theory is that this would of course be a lot faster. Aaron Stone, an
>> engineer at Six Apart, was helping me with the project (read: he did all the
>> work), but we are still not finished. Is there interest in exploring this
>> option further on this group?
>> 
>> Byrne
>> 
>> 
>> On 2/12/08 10:42 AM, "Reed A. Cartwright" <reed at scit.us> wrote:
>> 
>>   
>>> Hirotaka Ogawa wrote:
>>>     
>>>> I wonder about the feasibility of doing something after closing
>>>> connection, especially for CGI.  No doubt, it'll be feasible for
>>>> FastCGI.
>>>>       
>>> Yeah, it looks like the only way to do appendix tasks with CGI is to
>>> fork.  Oh well, one more reason to go to FastCGI.
>>>     
>> 
>> _______________________________________________
>> MTOS-dev mailing list
>> MTOS-dev at sixapart.com
>> http://www.sixapart.com/mailman/listinfo/mtos-dev
>> 
>>   
> 
> _______________________________________________
> MTOS-dev mailing list
> MTOS-dev at sixapart.com
> http://www.sixapart.com/mailman/listinfo/mtos-dev