Thanks. I read this links and have played with environment setings for lsapi.
What about number of retries on a failed requests. Is it possible to add a configuration parameter or at least server startup key-option. Let me elaborate why.
Just imagine web2 application based on Ruby. Ruby is very popular now, but it slow, very slow sometimes. An web2 application has ajax with all its powers and blemishes. It interactive but use a number requests across browser and server side. So its unreal to restrict a number request from host for a time interval, isn' it? From anothaer hand on server side we have Ruby on Rails with couple slow requests, no matter is it Ruby or slow DB connection. Those request should return something or nothing but to be in a time. Let say they draw a chart somther on user page or "processing" picture against chart if information is not actual. So those request could draw it quicly asap but sometimes freeze. Time limit is 2 minute. User excepts to see the chart and knows that in worst case it be or not after couple minute. But in our case we restrict time per request with 120 sec. And... User will not wait 6 minute(! server will try to receive response 3 times). User will refresh a page thinking that something wrong with connection, browser etc... So it refresh the page and send new requests which will processing again 3 times. And the previuse request is still processing same time. Another request is going for processing as well. So server need to fork new instances to proces them. It seems like DOS's timer bomb, doesn't it?
In this case can I ask you for configuration parametr about number of retries on failures requests for a future release.
Thank you in advance