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

[whatwg] Issues with Web Sockets API

From: Kristof Zelechovski <giecrilj@stegny.2a.pl>
Date: Sat, 27 Jun 2009 11:07:46 +0200
Message-ID: <41529A1EF741431F8166276B23ECA9D9@POCZTOWIEC>
Cellular phone signal strength bars are not implemented on top of Web
Sockets so this cannot make a use case.  This is rather a hardware thing.

On the other hand, I concur that a network queue overflow should be handled
differently than an out-of-memory condition.  For example, if you have an
infinite enumerator sending data to memory ? la chargen service, an overflow
failure is guaranteed and the programmer will have to do something about it;
on the other hand, if the same enumerator sends data to a network, the
failure will be random, depending on enumerator speed, network throughput
and receiver capabilities.

I think that the output buffer should not grow unbounded and the sending
worker should be stopped while the buffer is full.

Cheers,

Chris

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20090627/1a383391/attachment.htm>
Received on Saturday, 27 June 2009 02:07:46 UTC

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