From Ratchet to ReactPHP #534
Replies: 4 comments 1 reply
-
Hey @programarivm, good question, but first I'm interested in why you want to switch from Ratchet to ReactPHP. Ratchet itself builds on top of ReactPHP, so you're already using ReactPHP under the hood and switching completely means you would loose the WebSocket part of Ratchet. In conclusion, if you want to keep using WebSockets, you would then have to build the whole thing yourself. FYI: We're aware of Ratchet's current state and are already working on compatibility with the newest PHP and PHPUnit versions as described in ratchetphp/Ratchet#1025 (comment). One solution could also be Framework X here, as this project also builds on top of ReactPHP and is very easy to work with. The WebSocket documentation for Framework X is still under construction, but @clue explained how to set this up with Framework X in clue/framework-x#85 (comment). In the future we also want to have WebSockets build into Framework X, so it's even easier to use. Hope this helps 👍 |
Beta Was this translation helpful? Give feedback.
-
Thank you @SimonFrings, we'd use ReactPHP instead of Ratchet because it is an actively maintained repository. |
Beta Was this translation helpful? Give feedback.
-
Finally, the WebSocket chess server will be sticking to Ratchet because it is just working as expected. Also, we're writing a functional test suite that should also work for a TCP socket. We're considering two different solutions: A WebSocket server using Ratchet as well as a TCP socket using ReactPHP. Thank you, and keep it up! |
Beta Was this translation helpful? Give feedback.
-
👋 Hi there,
We're thinking along the lines of refactoring the PHP Chess Server and use ReactPHP instead of Ratchet.
Is there any good tutorial on how to do so?
Thanks for the help,
Beta Was this translation helpful? Give feedback.
All reactions