Ratchet VS AutoRoute

1) Do we must need to use some 3rd Party APIs or Libraries like Ratchet, PHP-Push-WebSocket or PHP WebSocket to enable PHP to communicate over WebSocket protocol?

I am using http://socketo.me/ to create the socket server.

Sockets: https://github.com/reactphp/socket WebSocket: https://github.com/ratchetphp/Ratchet

Have you considered using web sockets? Check out Ratchet PHP http://socketo.me/. Once the client and server make a connection your server can send notifications to the client while that connection is open.

How should I implement these functions? I am successful with using this documentation to implement basic websocket functions. However, I am still unable to subscribe to a channel/topic. The code is long so I put a github question here. Hope that you can help me with this.

You can do native websockets with PHP, but it's not straightforward with Laravel. Laravel Echo helps handle the client-side of websockets, but you need to manage the server side on your own.

Nice work. I have something similar I built on Ratchet, I looked at Socket.io in the early days but shelved plans to run a Node backend. Your front end looks a lot more appealing than mine does. ;)

However, the websockets server is based on a php package http://socketo.me/ , and sometimes that mini-app goes down without warning, leaving the chat to fallback to an old-school chat-archive. Even monitoring and being certain that the chat websocket server is -up- isn't obvious.

Hello, I have just start to learn web socket in php but I have one issue I would use a secure web socket for https pages but one their website: https://socketo.me They use a class, MyChat but vscode doesn’t find it. Does anybody know ? Thanks

Which implementation would you like? * http://socketo.me/ * https://amphp.org/websocket-client/ * https://www.swoole.co.uk/docs/modules/swoole-websocket-server

Also if you use a convention-based approach to your routes instead of hardcoding them you can support any number of routes. Something like how pmjones/AutoRoute and CodeIgniter's AutoRouting work.

You may wish to take a look at AutoRoute. I am the lead, and you can see benchmarks for it here.

This sounds remarkably similar to AutoRoute.

Interesting; AutoRoute is 2x faster than FastRoute in common cases; see benchmark. And it's pretty feature-filled at that.

There is another alternative: AutoRoute automatically maps incoming HTTP requests (by verb and path) to PHP action classes in a specified namespace. No more route files or annotations/attributes.

Might be nice to see AutoRoute included in the mix; it too is faster than FastRoute, and has some interesting additional features.

Not to yammer on about it, but that is exactly what AutoRoute does.

Nice! I'd be interested to see how it fares against AutoRoute -- benchmarks against FastRoute here.

You might additionally appreciate this: https://github.com/pmjones/AutoRoute