Jim Jagielski wrote:
On Aug 18, 2006, at 12:40 PM, Mladen Turk wrote:
The Tomcat should be responsible for deciding
if the connection will be reused or not.
This doesn't match, iirc, how the whole cache_timeout
(or connection_pool_timeout) is done within mod_jk...
Basically, what's needed is a way to make each
AJP a one-shot.
Right, but it should be in the form:
1. mod_jk/mod_proxy_ajp connects
2. Tomcat responds if the connection
'should/should not' be closed after the
response.
This way we would not end up with half-closed
socket problems. Further more, its part of AJP
spec, so what's the problem of implementing it?
Tomcat should have a directive that would tell
to close the connection after the response has
been send.
Regards,
Mladen.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
