-
-
Notifications
You must be signed in to change notification settings - Fork 139
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
2.0 is coming #42
Comments
Hello!! I just dropped here to say hi and to thank you for this project!! Version 2.0 looks promising!! |
hi, why Ratchet will be replaced by a gos fork? :| |
Hi, @gittix09 In fact , all the things present in the 2.0 version is already out in the latest version :) v2 will be a clean up. I can't say any date of released because i'm really busy. @patie In order to have a proper implementation of push integration, I have to insulate the TopicManager to share it across service instead of copy each connection in push service and in topic. I have keep the same namespace it's a fork with patch. The day of ratchet will resolve it, I will remove the fork. Next version will v0.4 and contains an lot of BC break so I think I will release another major version on my side. |
@Prophet777 which version of WAMP use this lib / which authobahn.js is needed? thx |
We use Wamp v1 with authoban 0.8 at least. (all is packaged inside the bundle). |
+1 Hello, Really need v2 WAMP cause of use in ReactJS with last version of autobahn... |
Ratchet do not plan to use wampV2, so it's not plan for websocketbundle sorry. |
Multiple applications on the same server - single websocket server?聽#47 Multiple application routing (@MuddyPaw)Topic pipeline聽#38 Pipelining (@ewertoncode)The text was updated successfully, but these errors were encountered: