Hi,
I have problem to keep the http connection alive with AsyncWeb. The
BasicServiceContainer uses CounterKeepAliveStrategy to determine if to
keep the http connection alive. Decision of its parent class
BasicKeepAliveStrategy is based on protocol version and client request
header. CounterKeepAliveStrategy adds counting of subsequent requests
and starts to break the http connection if the number of requests exceed
some limit.
The problem: There is one instance of CounterKeepAliveStrategy per
server container. This means that the counter is shared by all TCP
connections. In my case first 75 http responses to server has
'Connection: keep-alive' in header and then all subsequent responses
always has 'Connection: close' independently on actual TCP connection.
I think that BasicKeepAliveStrategy should be the default choice for
http container and if there is any need for CounterKeepAliveStrategy,
then it should keep the request count per one TCP connection (maybe
using IoSession attributes).
Best regards,
Jan Taus
MINA version: 2.0.0-M4
AsyncWeb version: svn trunk 752431 (Last Changed Date: 2009-03-03
18:59:26 +0100 (Tue, 03 Mar 2009))
--
Jan Tauš
Software Engineer
----------------------------
Acision - Innovation Assured
www.acision.com
Na Okraji 335/42
162 00 Praha 6
Czech Republic
T: +420 225 399 302
E: [email protected]
This e-mail and any attachment is for authorised use by the intended
recipient(s) only. It may contain proprietary material, confidential
information and/or be subject to legal privilege. It should not be copied,
disclosed to, retained or used by, any other party. If you are not an intended
recipient then please promptly delete this e-mail and any attachment and all
copies and inform the sender. Thank you.
