- From: <piranna@gmail.com>
- Date: Wed, 7 May 2014 17:28:35 +0200
- To: Iñaki Baz Castillo <ibc@aliax.net>
- Cc: "public-webrtc@w3.org" <public-webrtc@w3.org>
I would find it better that process gets blocked until the buffer gets some space available (it's said, it has send something), or raise an error or throw an exception but NO close the channel... Too much agressive to my taste, specially without being able to know how to preven it... 2014-05-07 17:19 GMT+02:00 Iñaki Baz Castillo <ibc@aliax.net>: > Hi, according to the spec (and this is the same for WebSocket): > > "if the data cannot be sent, e.g. because it would need to be buffered > but the buffer is full, the user agent must abruptly close channel’s > underlying data transport with an error." > > OK, I can check the current buffered data size via > socket.bufferedAmount. But, how may I know the buffer value that would > cause send() to fail *without* calling send()? > > If the buffer size is not standardized, shouldn't the API provide a getter? > > Thanks a lot. > > -- > Iñaki Baz Castillo > <ibc@aliax.net> > -- "Si quieres viajar alrededor del mundo y ser invitado a hablar en un monton de sitios diferentes, simplemente escribe un sistema operativo Unix." – Linus Tordvals, creador del sistema operativo Linux
Received on Wednesday, 7 May 2014 15:29:24 UTC