-
Notifications
You must be signed in to change notification settings - Fork 17
WebSocket support #100
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
WebSocket support #100
Conversation
Conflicts: package.json
Current coverage is 100% (diff: 100%)@@ develop #100 diff @@
=====================================
Files 11 15 +4
Lines 1446 1627 +181
Methods 228 278 +50
Messages 0 0
Branches 365 393 +28
=====================================
+ Hits 1446 1627 +181
Misses 0 0
Partials 0 0
|
+1 |
1 similar comment
+1 |
* @param index - Database index | ||
* | ||
* @constructor | ||
* @param address - Server name or IP Address to the Kuzzle instance |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't we rather use host
instead of address
?
Looks to me to be more standard and more accurate.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done. I've also fixed a potential bug with the off
function in websocket wrappers (node + browser)
Apart from the host/address naming thing, +1 |
Add pure WebSocket capabilities to the Javascript SDK, while still supporting SocketIO to ensure compatibility with older browsers.
Unrelated changes
Kuzzle.query
is invoked without a query argument. Now throws an error when such a case occursresponseCallback
JSDoc