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

[whatwg] Issues with Web Sockets API

From: Robert O'Callahan <robert@ocallahan.org>
Date: Tue, 28 Jul 2009 12:48:30 +1200
Message-ID: <11e306600907271748v36e2ac7es9d414139b36a7fd3@mail.gmail.com>
Why not just allow unlimited buffering, but also provide an API to query how
much data is currently buffered (approximate only, so it would be OK to just
return the size of data buffered in user space)?

Then applications that care and can adapt can do so. But most applications
will not need to. The problem of partial writes being incorrectly handled is
pernicious and I definitely think partial writes should not be exposed to

"He was pierced for our transgressions, he was crushed for our iniquities;
the punishment that brought us peace was upon him, and by his wounds we are
healed. We all, like sheep, have gone astray, each of us has turned to his
own way; and the LORD has laid on him the iniquity of us all." [Isaiah
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20090728/b94e83e5/attachment.htm>
Received on Monday, 27 July 2009 17:48:30 UTC

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