b/f: Result: autobahn.js expects the details object to be non-null #76
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
|
Looks good to me. @jcelliott, do you know of anywhere else where we may have missed something similar? This looks like a fix for #72. |
same problem as with RESULT message
|
Found the same problem with the INVOCATION message and autobahn.js. Will further test against autobahn.js |
|
I ran into the same problem. A merge would be nice. |
jcelliott
added a commit
that referenced
this pull request
May 21, 2015
b/f: Result: autobahn.js expects the details object to be non-null
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
According to the WAMP specification the RESULT message send by the dealer should have the following format:
[RESULT, CALL.Request|id, Details|dict]
i.e. the Details dict should be non-null. Autobahn.js relies on this.