[whatwg] Issues with Web Sockets API

Darin Fisher darin at chromium.org
Fri Jun 26 21:18:53 PDT 2009


On Fri, Jun 26, 2009 at 3:16 PM, Drew Wilson <atwilson at google.com> wrote:

>
>
> On Fri, Jun 26, 2009 at 2:11 PM, James Robinson <jamesr at google.com> wrote:
>
>>
>>
>> Forcing applications to build their own send/ack functionality would be
>> pretty tragic considering that WebSockets are built on top of TCP.
>>
>> - James
>>
>
> Every time I've written a response/reply protocol on TCP I've needed to put
> in my own acks - how else do you know your message has been delivered to the
> remote app layer?
>

This seems especially true given that WebSocket connections may be proxied.

-Darin



>
> One could argue that WebSockets should do this for you, but I like leaving
> this up to the app as it gives them more flexibility.
>
> -atw
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20090626/8a036e24/attachment-0002.htm>


More information about the whatwg mailing list