Alternative to Ratchet for WebSocket?

[jdeepwell]

Hi all,

I have implemented a WebSocket server using ReactPHP/Ratchet. To be honest I am loosing a little faith in the development of Ratchet and the fact that it uses so much deprecated stuff from PHP worries me. I therefore started looking for alternative WebSocket implementations that work nicely with ReactPHP – but by now to no avail :(

So I just wanted to reach out if anyone would have a pointer. Is there really no alternative to Ratchet? (I would really like to avoid having to switch to AMPHP....)

[WyriHaximus]

Have a look at https://github.com/voryx/WebSocketMiddleware it uses the Ratchet's websocket implementation under the hood.

[jdeepwell]

Hey @WyriHaximus , thx for the reply!
Yes, I stumbled upon this too. It's just that if it depends on Ratchet (it requires part of it in its composer.json) it's not really an alternative to it.
J.

[WyriHaximus]

That's purely the RFC6455 implementation, that only has a dependency on Guzzle's PSR-7 implementation not everything Ratchet is self depends on: https://packagist.org/packages/ratchet/rfc6455

[jdeepwell]

I see – thx for pointing that out.
From what I can tell also non of ratchet/rfc6455's code has deprecations when targeting PHP 8.3 (which I am) – so that's good.
Will definitely give it a try!

[WyriHaximus]

Keep us posted 👍

[jdeepwell]

Was off to a slightly rocky start 'cause the current example code in the WebSocketMiddleware Readme uses deprecated ReactPHP classes. But that gave me the kick I needed to also update all my ReactPHP stuff to the current versions. After that and going through the WebSocketMiddleware examples it was fine – it's not a drop-in replacement, but the changes are manageable. Works great and I finally was able to remove the error_reporting(E_ALL ^ E_DEPRECATED); (which right away lead to catching an issue in my code :)

Thx again for the hint!