phpsocket.io VS Socket.io

You can run a node js with socket Io as a WebSocket service and then use Apache to proxy it, you could still use your HTML served by Apache with no problem. Also, there's an implementation of socket Io written in PHP, maybe it worth take a look https://github.com/walkor/phpsocket.io

If neither works I do not have experience with the next. But a Socket.io type implementation could work. Could make a simple web API in node to handle just the events/web sockets. Can also look around to see if anyone has made any implementations of Socket.Io for php that would work with the Socket.Io JS client library. Here's one, don't know if it works or how well.

In line 32 we have the socket.io editaData event which handles data editing in the server. When the user clicks edit in the client, the server searches for the data using the findIndex method. If it exists it updates the data in the crudData array then it broadcasts the edited data to the client.

Tools like Socket.IO and WebSockets significantly simplify the implementation of real-time communication between client and server.

To capture the test execution status, I wrote a custom karma reporter(a good resource) with which I was able to emit the test execution status back to the vscode extension. I am using socket.io to do this communication.

Building such experiences is already possible, using libraries such as socket.io and React Together. This blog post explains how to easily add real-time collaboration to an existing React app, using React Together.

Complexity: WebSockets require you to handle connection lifecycle events, such as errors and reconnections. While the code example I provided could suffice for simple use cases, more complex use cases might arise, like automatic reconnection and queueing messages sent by the client when the connection wasn't open. For that, you can either extend this code or use an external library like react-use-websocket for a relatively lightweight react implementation or socketio for both client and server SDKs.

Socket.IO

aiortc can be easily integrated with other python libraries such as aiohttp for web server as well as other third party libraries such as socket.io for real time event handling

We need to allow users to get real-time updates when a new video, comment, or like is created or when a video is updated. To do this, we'll use Socket.IO. We'll write a custom Socket implementation in our Strapi project to handle real-time functionalities.

uWebSockets is web server written in C++. In our case we'll be using uWebSockets.js which has bindings to NodeJS. It can be used as a usual web server but the main feature is its WebSocket server. It is 10x faster than Socket.IO and 8.5x faster than Fastify. I have to say I haven't benchmarked it myself. I decided to use uWebSockets just because it feels more pure to my taste. For example it doesn't require Express it runs on it's own, also it doesn't have any additional wrappers or helper functions that "babysit" you. You just get a message and you handle it whatever the way you want it. So if you're ok with that approach and you need a faster WebSocket server then you should use uWebSockets.

This tutorial will guide you through building a real-time notification system for a chat app using React and Socket.io. React is ideal for creating dynamic, reusable components and efficiently managing your app’s state. Socket.io enables real-time, bidirectional communication between the server and the browser, allowing instant message delivery without page reloads. This combination lets you build a responsive, interactive UI that communicates with the server in real-time.