*cc'ing others involved in WebSockets (server and client side) I'm not very familiar with the IETF's efforts, but my understanding is that they were creating a competing protocol. Are they in fact creating something that they want to submit as a replacement to WebSockets? If so, why is WebSockets moving to last call?
I'm not necessarily against this change, just confused by it. * On Fri, Nov 13, 2009 at 10:03 AM, Alexey Proskuryakov <[email protected]> wrote: > > While WebSocket API is fairly stable, the discussion of underlying protocol > at IETF is far from being done. It could be disruptive to ship our WebSocket > implementation in a way that would effectively freeze the protocol. > > One way to achieve future compatibility is by using a different scheme for > WebSocket URLs - e.g. "webkit-ws:" and "webkit-wss:" instead of "ws:" and > "wss:", respectively. Depending on how protocol standardization goes, we > could alias these later, or add a separate standards compliant > implementation. > > I'm going to submit a patch to this effect, but would like to discuss the > idea on the list first. > > - WBR, Alexey Proskuryakov > > _______________________________________________ > webkit-dev mailing list > [email protected] > http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev >
_______________________________________________ webkit-dev mailing list [email protected] http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
