3 ms·
What PHP needs is the ability to run websockets natively without extra setup. Right in a mod_php or PHP-FPM. None of the current platforms have this right. You
by bungle 14y ago
What PHP needs is the ability to run websockets natively without extra setup. Right in a mod_php or PHP-FPM. None of the current platforms have this right. You always have to run extra web servers in place of Apache or Nginx. Yes, this is also a thing that Apache, and Nginx have to figure out. Running node.js or Go web servers is too immature.
- j_baker 14y agoIf you're afraid of immature technologies, why use websockets to begin with?
- bungle 14y agoGood question. I see this more or less like chicken-egg situation. Right now it seems that client side is quite well maturing. Client side is the easier part of websockets. PHP's whole model is 'shared nothing', that's why it fits so poorly with websockets. 'Real-time' two-way communication with the server and the clients is getting more and more common in web apps, and even web sites. I'm not sure how the server side of the websockets are going to be solved. If PHP gets it right, it will probably have great future ahead. These days we need to revert to dual solution, main system behind Apache or Nginx, and websockets with for example custom node.js servers. It is far from optimal.
- astrodust 14y agoIt'd be far easier to fix any problems you have with node.js than to extend PHP to make this practical.