- From: Bjoern Hoehrmann <derhoermi@gmx.net>
- Date: Fri, 31 Aug 2012 23:32:59 +0200
- To: Randell Jesup <randell-ietf@jesup.org>
- Cc: "public-webrtc@w3.org >> \"public-webrtc@w3.org\"" <public-webrtc@w3.org>
* Randell Jesup wrote:
>The API, per the decisions at the Interim and mailing list is based
>closely on the WebSockets interface. For example, you are supposed to
>wait for onopen to fire before calling send(), at both ends. (The
>low-level IETF protocol supports sending before onopen, but WebSockets
>doesn't.) Currently I have no limit on send(DOMString); WebSockets
>limits DOMStrings to 123 characters.
The length limitation is in bytes, not characters, and only on .close
for reason phrases ("I am closing the connection because the computer
is going to reboot now"); the API does not allow you to queue messages
to be sent if and once a connection has been established, but that is
not different from the underlying protocol, the concept does not exist
at that level.
--
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/
Received on Friday, 31 August 2012 21:33:24 UTC