Websocket server with PHP

Question

I'm currently developing a PHP application that is going to use websockets for client-server communication. I've heard numerous times that PHP shouldn't be used for server applications because of the lack of threading mechanisms, its memory-management (cyclic references) or the unhandy socket library.

So far, everything is working quite well. I'm using phpws as the websocket library and the Doctrine DBAL to access different database systems; PHP is version 5.3.8 . The server should serve a maximum of 30 clients. Yet especially in the last days I've read several articles stating the ineffectiveness of PHP for long running applications.

Now I'm not aware whether I should continue using websockets with PHP or rebuild the entire serverside application. I've tried Python with Socket.IO, though I did not get the results I expected.

I guess I have the following options:

Keep everything as it is.
Make the application use Ajax in combination with Socket.IO - e.g. run a serverside script that invokes the client's ajax calls when data is submitted to the server.

The last point sounds quite interesting, though it would require some work .. Would it be a problem for servers to execute all the clients requests at one time?

What would you recommend? Is the problem with PHP's memory management (I'm using gc_collect each time a client sends data to the server) still valid? Are there other reasons beside the obvious reasons (no threading, ...) for not using PHP as a server?

So you're asking if you should scrap your current, working, design? Questions like this aren't really valid here, you're going to have to decide what to code it in yourself. What other server side languages do you know? Post your python code and someone can help find the problem if you do decide to rewrite your code. — xthexder
– xthexder, Commented Aug 17, 2012 at 13:36

Bruno Gagnon-Adam · Accepted Answer · 2012-08-17 17:23:49Z

4

You can try running your socket.io on a node server on another port on your server (that is if you are not using a hosting plan like goDaddy).

I am using it and the performances are really satisfying. I have an apache server on the port 80 serving my php files, and my server-client communications are done using a Node.js server running socket.io on the port 8080 (dev) or 843 (prod).

Node.js is really light and has great performance, but you need to run it as a server. Nodejitsu.com is a hosting solution that has the websocket protocol available and is on beta, so it is still free for now. Just note that you need to listen on the port 80 with socket.io, this is a limitation from theyr network.

If you want your pages all to be accessed on the port 80 then you will need a reverse proxy like varnish .

I hope that helps! Have a nice day.

answered Aug 17, 2012 at 17:23

Bruno Gagnon-Adam

7476 silver badges16 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Soundz · Accepted Answer · 2012-08-17 13:46:02Z

0

Are there other reasons beside the obvious reasons (no threading, ...) for not using PHP as a server?

Yep, lots of socketfunctions are incompatible with each other and it's a hell to debug.

i tried something similar myself and quit frustrated sind every function i thought would make sense didnt do what i expected

answered Aug 17, 2012 at 13:46

Soundz

1,30010 silver badges17 bronze badges

Collectives™ on Stack Overflow

Websocket server with PHP

2 Answers 2

Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related