Alvaro Lopez Ortega wrote:
> Damn it!! I knew something like this would happen. :-/
>
> There is something that doesn't much sense though. The PHP server
> accepts multiple connection.. what for? :-? I'm gonna take a look
> at the code to try to figure out that is the reason for that od
Mohammad DAMT wrote:
>> > * Put the managers into a one static table for all threads so it
>> > will not be re-created all the time.
>>
>> The idea is to allocate FastCGI managers per thread. In this
>> way, it is consistent (connections never change of thread) and we
>> don't need semapho
Pada hari Minggu, tanggal 11/12/2005 pukul 18:34 +, Alvaro Lopez
Ortega menulis:
> Hi Mohammad,
>
> > * Put the managers into a one static table for all threads so it
> > will not be re-created all the time.
>
>The idea is to allocate FastCGI managers per thread. In this way,
>it
Hi Mohammad,
> * Put the managers into a one static table for all threads so it
> will not be re-created all the time.
The idea is to allocate FastCGI managers per thread. In this way,
it is consistent (connections never change of thread) and we don't
need semaphores to protect the stat
Hi,
Please find some FastCGI fixes to the trunk as attached. What it does:
* Put the managers into a one static table for all threads so it will
not be re-created all the time.
* Put the connection to blocking mode, this was done to make debugging
easier. It could be turned off later.
* Added fcg
