At 9:56 Uhr +0100 11.10.2000, Stephen Anderson wrote:
> > -----Original Message-----
>> From: Perrin Harkins [mailto:[EMAIL PROTECTED]]
>> Sent: 11 October 2000 04:45
>> To: Ajit Deshpande
>> Cc: [EMAIL PROTECTED]
>> Subject: Re: Wild Proposal :)
>>
>>
>> Hi Ajit,
>>
>> It's not entirely clear to me what problem you're trying to
>> solve here.
>> I'll comment on some of the specifics you've written down here, but I
>> may be missing your larger point.
>
>Ajit's examples aren't perfect, but the problem is a real one. The problem
>is one of generalisation. Logically, you don't want to put an application
>that is 10% web-related into mod_perl. So, you can take out the other 90%
>and stick it into an RPC server, but wouldn't it be nice if there was an
>application server framework that handled connections,load balancing and
>resource management for you?
Isn't FastCGI handling exactly this?
Maybe what's missing currently is a fastcgi framework (a perl module
in the fastcgi process) for handling stuff like reloading
scripts/parts of the application when they change, handling database
connections etc. There don't seem many people using fastcgi (with
perl) currently. This is the reason I wrote everything myself for my
fastcgi applications (see testwww.ethz.ch/eile, shameless plug once
again :-), and I think it would be good to have some more general
stuff like this (more generic than my framework).
Christian.
