Comment #23 on issue 761 by [email protected]: Incorrect UTF-8
encoding/decoding for non-BMP characters in String related functions
http://code.google.com/p/v8/issues/detail?id=761
Hi, I'm a developer of WebSocket.
I couldn't reproduce the issue on my local environment (WebSocket received
non-BMP characters correctly).
Please check out:
- WebSocket only accepts UTF-8 encoded data in text frames. (UTF-16 is not
allowed.)
- WebSocket has its own frame format; you need to append frame header
before your text data.
- Since Chrome 14, WebSocket protocol implementation has been changed to
comform to the recent protocol. You may need to update your server
implementation so it conforms to
<http://tools.ietf.org/html/draft-ietf-hybi-thewebsocketprotocol-10>.
If you still believe this is a bug, feel free to open a new Chromium bug
with detailed information (version number, OS, steps to reproduce, etc.)
from <http://new.crbug.com/>.
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
