Browse files

Suggest using SockJS 0.3 not 0.2

  • Loading branch information...
1 parent 698fb5a commit d3e704a7b96b0c4fba6d80126d598c649a0da34b @majek majek committed Apr 14, 2012
Showing with 5 additions and 5 deletions.
  1. +5 −5
@@ -85,7 +85,7 @@ but instead of `WebSocket` there is a `SockJS` Javascript object.
First, you need to load SockJS JavaScript library, for example you can
put that in your http head:
- <script src="">
+ <script src="">
After the script is loaded you can establish a connection with the
@@ -229,7 +229,7 @@ Connecting to SockJS without the client
Although the main point of SockJS it to enable browser-to-server
connectivity, it is possible to connect to SockJS from an external
-application. Any SockJS server complying with 0.2 protocol does
+application. Any SockJS server complying with 0.3 protocol does
support a raw WebSocket url. The raw WebSocket url for the test server
looks like:
@@ -248,14 +248,14 @@ In order to utilize best performance you should use the SockJS-client
releases hosted on SockJS CDN. You should use a version of sockjs-client
that supports the protocol used by your server. For example:
- <script src="">
+ <script src="">
A list of files hosted on a CDN is available here: .
You can also use or CDN via https (using Cloud Front domain name):
- <script src="">
+ <script src="">
For server-side deployment tricks, especially about load balancing and
@@ -322,7 +322,7 @@ server. Edit the [`config.js`](
And replace `sockjs_url` setting which by default points to CDN:
- sockjs_url: '',
+ sockjs_url: '',
to a freshly compiled sockjs, for example:

0 comments on commit d3e704a

Please sign in to comment.