This repository has been archived by the owner on Mar 6, 2018. It is now read-only.
Fix message format #51
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
[message type] ':' [message id ('+')] ':' [message endpoint] (':'
[message data])
|
I have also seen problems with escaping of quotes that using Chrome to Chrome does not do... but using this library to Chrome results in all the quotes being escaped on socket.emit |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The expected message format is:
[message type] ':' [message id ('+')] ':' [message endpoint] (':'[message data])The existing implementation inserts an extra ':' at the end if there is no data.