<div><i><span class="Apple-style-span" style="font-style: normal; "><i>cc'ing others involved in WebSockets (server and client side)</i><div><br></div><div>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?</div>
<div><br></div><div>I'm not necessarily against this change, just confused by it.</div></span></i><div><br><div class="gmail_quote">On Fri, Nov 13, 2009 at 10:03 AM, Alexey Proskuryakov <span dir="ltr"><<a href="mailto:ap@webkit.org" target="_blank">ap@webkit.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
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.<br>
<br>
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.<br>
<br>
I'm going to submit a patch to this effect, but would like to discuss the idea on the list first.<br>
<br>
- WBR, Alexey Proskuryakov<br>
<br>
_______________________________________________<br>
webkit-dev mailing list<br>
<a href="mailto:webkit-dev@lists.webkit.org" target="_blank">webkit-dev@lists.webkit.org</a><br>
<a href="http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev" target="_blank">http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev</a><br>
</blockquote></div><br></div></div>