Been a long time since I wrote "realtime" code in PHP, but... the docs here say
>>>What a "real-time PHP app" used to require
nginx for reverse proxy and static files. php-fpm to run PHP. Node.js for a Socket.IO server"
PHP has socket_create, socket_bind, socket_listen (also the lovely socket_set_nonblock), all available to write a pretty simple daemon that listens, spawns worker processes (which can listen on their own sockets) and orchestrates the streams back to the client in pure PHP. I don't see any reason you'd need to run Node.js to manage socket communication if you wanted your architecture to be PHP.
Interesting.
Been a long time since I wrote "realtime" code in PHP, but... the docs here say
>>>What a "real-time PHP app" used to require
nginx for reverse proxy and static files. php-fpm to run PHP. Node.js for a Socket.IO server"
PHP has socket_create, socket_bind, socket_listen (also the lovely socket_set_nonblock), all available to write a pretty simple daemon that listens, spawns worker processes (which can listen on their own sockets) and orchestrates the streams back to the client in pure PHP. I don't see any reason you'd need to run Node.js to manage socket communication if you wanted your architecture to be PHP.
When you need a very fast alternative for speed