[Pkg-javascript-commits] [sockjs-client] 216/434: #29 Explain that we now support all unicode chars.

Tonnerre Lombard tonnerre-guest at moszumanska.debian.org
Wed Jan 8 00:47:14 UTC 2014


This is an automated email from the git hooks/post-receive script.

tonnerre-guest pushed a commit to branch master
in repository sockjs-client.

commit fc4f9dd2328646efe1259665fbded8b9f8491605
Author: Marek Majkowski <majek04 at gmail.com>
Date:   Fri Nov 25 17:26:48 2011 +0000

    #29 Explain that we now support all unicode chars.
---
 README.md | 11 +++++------
 1 file changed, 5 insertions(+), 6 deletions(-)

diff --git a/README.md b/README.md
index 755cb7e..c0be326 100644
--- a/README.md
+++ b/README.md
@@ -138,12 +138,6 @@ bad practice. If you absolutely must do it, you can use
 mutliple subdomains, using different subdomain for every
 SockJS connection.
 
-Currently SockJS-client is only able to send valid Unicode messages.
-Never try to send
-[unicode surrogates](http://en.wikipedia.org/wiki/Mapping_of_Unicode_characters#Surrogates),
-Less common characters can be badly encoded into UTF-8 due to various
-browser quirks, we're working a fix.
-
 
 Supported transports (#1)
 -------------------------
@@ -263,3 +257,8 @@ There are various browser quirks which we don't intend to address:
    connection to one domain at the same time.
  * You shouldn't start SockJS connection before `body` loads - don't
    create SockJS objects within `head` (see #15).
+ * Although SockJS is able deal with any Unicode characters (even
+   [invalid ones](http://en.wikipedia.org/wiki/Mapping_of_Unicode_characters#Surrogates),
+   it's advisable to use only valid characters. Using invalid
+   characters is a bit slower, as SockJS must escape them before
+   sending over the wire.

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-javascript/sockjs-client.git



More information about the Pkg-javascript-commits mailing list