----- Original Message ----- > From: "Costin Manolache" <cos...@gmail.com>
> > I haven't looked at the tomcat6/tomcat7 interfaces, but I think the > current > hook mechanism used by spdy could be ported with minimal risk and > could be > used by websockets. Tomcat 7 may be a candidate. Tomcat 6, If I was an administrator, I would not expect any code changes like that in a dot release. > > All we need in both cases is for the request to stop being processed > by the > original protocol, and to have direct access to the socket. Than spdy > can > do its multiplexing and websocket can keep the socket alive and let > the > original request headers go away. Yes, I'd like to see some real numbers on the request header overhead. I doubt it will be an issue for Tomcat 6. For Tomcat 7 large refactorings and optimzations are happening all the time, so in there it makes sense. > > The hard part for spdy backporting is getting the SpdyProcessor - > i.e. the > virtual/multiplexed request/response, not associated with a real > socket. ( > which still requires lots of work on trunk, to get the rest of the > features > - comet, websocket-over-spdy, etc ). Not sure how hard it'll be to > backport, but still it shouldn't be very risky. As I just got back into the code mode of Tomcat, I'll look forward to take a look and see how it progresses. Filip --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
