On Jul 15, 2013, at 10:59 AM, Thach Tran (thactran) <thact...@cisco.com> wrote:
> Hi, > > I am currently looking at proxying WebSocket connections through ATS to a > WebSocket-enabled backend. As far as I can see, ATS is not supporting this at > the moment and there's only a couple of brief discussions about this in the > past on the mailing list. Could someone be able to comment a bit more on the > current state of this? I'm not aware of anyone working on this. What is needed is a way for plugins to register on an upgrade name and for the HTTP state machine to send connections across to the plugin when it sees the upgrade header. The API should look similar to TSNetAcceptNamedProtocol(). > Also, has anybody gotten around to start experimenting on a plugin or a patch > that could support this? If so, would you mind sharing some code examples or > ideas with the wider community so that it can server as a starting point. I > think supporting WebSocket would be a great feature to add to ATS generally > anyway since there seems to be more and more demand for it. I'm happy to provide guidance or code review if you are interested in working on this. > > Any help would be very welcome. > > Regards, > Thach
