Jamie Lokier wrote: > An interesting idea I've looked at, which would be tricky but _really_ > improve widespread support (and compatibility), would be to send > something which looks like a valid HTTP long-polling request, and > allow the server and any proxies to proactively signal that they'll > convert it to the more efficient WebSocket - when they will. When > they won't, communication continues over HTTP long-polling, carrying > the same messages and subprotocols over that. I guarantee if that > could be pulled off, everyone would start using WebSocket asap ;-) Cometd-2 (in alpha state) is more or less doing this already. It should be in beta release shortly and then any cometd client will be able to use websockets if the browser has it and the server handshake says that the server supports it. Otherwise it is long polling business as usual. regards
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.