- From: Iñaki Baz Castillo <ibc@aliax.net>
- Date: Wed, 7 May 2014 18:30:55 +0200
- To: "piranna@gmail.com" <piranna@gmail.com>
- Cc: "public-webrtc@w3.org" <public-webrtc@w3.org>
2014-05-07 18:15 GMT+02:00 piranna@gmail.com <piranna@gmail.com>: >>> or raise an error or throw an exception >> >> That's the same :) >> And yes, the implementation (at least in Chrome) does raise an error >> (BTW an undocumented kind of error, of course, as most of the WebRTC >> errors...). > > Why do you think it's the same? I meant that raising an error or throwing an exception is basically the same :) >>> but NO close the channel... Too much agressive to my taste, specially without being able to know how to >>> preven it... >> >> I agree. Anyhow: I've tested that Chrome does NOT close the socket >> after raising the error. This is, you can send data after some time on >> the same socket. > > I think this is the correct behaviour, but it would be better to get > notified when you can send data again (.send() method returning a > promise?). Probably. Anyhow, IMHO the current Chrome behavior is good enough (fire an error if the sending buffer is full, but don't close the connection). -- Iñaki Baz Castillo <ibc@aliax.net>
Received on Wednesday, 7 May 2014 16:31:41 UTC