> I have read in some places on the net that PHP is not suitable for WebSockets due to it's nature. That WebSockets are designed for long running threads/processes which each maintain multiple event-driven connections, whereas PHP was designed around the short-lived single process procedural paradigm. Well, you could certainly run into trouble if you're not careful. For example, using an Apache module PHP installation would not likely end nicely :) > Yet on the other hand I see lots of guides and libraries (such as http://socketo.me/) on the net that deal with PHP WebSockets. So I don't know what to think at this stage. Is PHP a suitable platform for developing a web application that requires WebSockets? I'm sure you could get get your application running with PHP. That said, I personally would not use PHP for the web socket implementation in my stack. I'd probably use Go, node.js or even Erlang for the web socket server itself (non-blocking IO is baked into these environments, which is handy for limiting the resources required for this type of application), but I'd likely use PHP for components that weren't directly tied to the web sockets (db frontend, etc.) Obviously, that's just my personal preference, and as you've noted, people are doing nice things in the web sockets world with PHP, so it can be done. That said, I suspect I'd have an easier time with one of the other languages for this particular aspect of an application, as the resource management should be much easier to manage. I don't think there's a "right" tool for the job, but I do believe some language environments may better facilitate this specific type of development. Have fun! Adam -- Nephtali: A simple, flexible, fast, and security-focused PHP framework http://nephtaliproject.com -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
