W3C home > Mailing lists > Public > whatwg@whatwg.org > June 2009

[whatwg] Issues with Web Sockets API

From: Drew Wilson <atwilson@google.com>
Date: Fri, 26 Jun 2009 15:16:03 -0700
Message-ID: <f965ae410906261516o6f5b9d56ye096840bca3876f9@mail.gmail.com>
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?

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.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20090626/546cd168/attachment.htm>
Received on Friday, 26 June 2009 15:16:03 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:13 UTC