-
-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unify websockets framing. #28
Comments
Bad news. Sockjs-client is using the form that isn't documented in the https://github.com/sockjs/sockjs-client/blob/67af34fc94df4fd08415c0d1aad6ad9dd2b048bc/lib/sockjs.js#L214 |
I decided to always use squares - like The disadvantage is two bytes more per message. But it will give us a tiny bit more flexibility in the future. (I'm thinking about support for binary data already). Hopefully this was long tested by sockjs-protocol so the core protocol doesn't need to change. |
Btw, the framing with square brackets was tested for a long time here: sockjs-protocol/sockjs-protocol-dev.py Line 550 in ae12ddf
|
i think all essential tests should be moved to latest version of protocol (WebsocketHybi10) or at least should be duplicated |
Agreed. Please file a bug if you have anything particular in mind. |
ah, i see sockjs-protocol-dev.py already sends message with square brackets |
Continued: #61 |
@mrjoes on the mailing list http://groups.google.com/group/sockjs/browse_thread/thread/709ae905e315e1a6 noticed that once in the sockjs-protocol we do:
and later:
The text was updated successfully, but these errors were encountered: