There is a deficiency in the asynch websocket stuff in trunk. For background, the websockets proxy acts like mod_proxy_connect after the initial setup. It can ask event to watch both sockets for it and return SUSPENDED.
But there is no separate timeout if neither end sees activity, so the request can stretch out a long time. My only idea here is: Fire off some separate timer event at a relatively long interval to see if the pair of sockets has been idle for a very long time (it would have the same baton as the other callback) Optionally, the timer event could be cancelled when the socket callback fires -- we would need to add a way to cancel those events. Otherwise, it would just try to grab the invoke mutex then check to see when the last socket activity was. Anybody have better ideas? -- Eric Covener [email protected]
