Re: msession tech note, 'feature' (buglet), call for
| From: | mlwmohawk at mohawksoft dot com | Date: | Wed, 13 Feb 2002 12:43:48 +0000 |
| Subject: | Re: msession tech note, 'feature' (buglet), call for | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-80008@lists.php.net to get a copy of this message | ||
> At 10:16 PM 2/12/2002 -0500, mlwmohawk@mohawksoft.com wrote:
>>There are a number of ways to deal with this, but creating a socket
>>pool of active sockets, and have a number of threads handle the sockets
>>in a classing queue fashion seems like the best way.
>>
>>Anyone have a better idea?
>
> Either do a thread pool like you mention here or if you want to get
> maximum performance you should consider non-blocking I/O. Check out
> http://state-threads.sourceforge.net/
The msession daemson does "no" I/O. It is a ram only system. The only I/O
it does do is to the network card. The network does not block unless I
code it to do so.