[Web-SIG] how to test hunging socket ?

[William Dode]

On 30-01-2009, Ian Bicking wrote:
> --===============1780478717==
> Content-Type: multipart/alternative; boundary=00163646d5c46749ac0461ba70c5
>
> --00163646d5c46749ac0461ba70c5
> Content-Type: text/plain; charset=UTF-8
> Content-Transfer-Encoding: 7bit
>
> On Fri, Jan 30, 2009 at 3:48 PM, William Dode <wilk at flibuste.net> wrote:
>
>> Fine, i should definitely give it a try.
>>
>> If my app is not thread safe but respond in a decent time, can i benefit
>> from a multithread server (for a socket problem) if i use a lock for
>> every page like that :
>>
>> I use webob...
>>
>
> If your app isn't threadsafe, you should use a multiprocess server.
> mod_wsgi has options for this, and flup has forking options (you'd use flup
> behind Apache or another server).

Yes, i also could use an async server. But i would like to identify (and 
reproduce) exactly the problem.
I also use a lot of cached data in my app. Anyway i have to make it 
thread-safe...

-- 
William Dodé - http://flibuste.net
Informaticien Indépendant