[webkit-dev] Staging WebSocket protocol deployment

Ojan Vafai ojan at chromium.org
Fri Nov 13 11:58:46 PST 2009


>
> This is a great idea. It would be a shame to put this out there and be
stuck with a crippling set of design decisions as happened with
LocalStorage. In practice, using WebSockets is a big enough change for web
developers that adding the webkit- is nothing more than a minor
inconvenience (if that) for early adopters.

>
Ojan

On Fri, Nov 13, 2009 at 11:14 AM, David Levin <levin at chromium.org> wrote:
>
>> There is the browser side:
>> http://www.w3.org/TR/2009/WD-websockets-20091029/
>>
>> In that spec, it says
>>
>>  This specification is being developed in conjunction with an Internet
>> Draft for a wire protocol, the Web Socket Protocol, available from the IETF
>> at the following location:
>>
>>
>>    - WebSocket Protocol Internet-Draft:
>>       http://tools.ietf.org/html/draft-hixie-thewebsocketprotocol
>>
>>
>>
>> On Fri, Nov 13, 2009 at 10:46 AM, Jeremy Orlow <jorlow at chromium.org>wrote:
>>
>>> *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 <ap at webkit.org>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
>>>> webkit-dev at lists.webkit.org
>>>> http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
>>>>
>>>
>>>
>>> _______________________________________________
>>> webkit-dev mailing list
>>> webkit-dev at lists.webkit.org
>>> http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
>>>
>>>
>>
>> _______________________________________________
>> webkit-dev mailing list
>> webkit-dev at lists.webkit.org
>> http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-dev/attachments/20091113/0046e1fe/attachment.html>


More information about the webkit-dev mailing list