I've been playing with this in my sandbox, it adds a "socket readable" callback to event, similar to the timed callback, which allows mod_proxy_wstunnel to hop on and off the thread like test/mod_dialup.
http://people.apache.org/~covener/websocket-asynch-8.diff The weird API for the socket callback, which treats a set of sockets as a group and only callbacks once per group, is to avoid hairy situations where something like wstunnel or mod_proxy_connect sees callbacks after the request has finished (or has to make sure this doesn't happen and use longer-lived pools for state). I didn't want to just dump the event side in trunk where it might fall through the cracks. -- Eric Covener [email protected]
