Categories
apache javascript mod-perl perl websocket

Most viable WebSocket/Perl solution

The company I’m working at uses Perl for all “backend related” stuff. However, we would like to use some real-time communication between server-processes and connected clients via browser.

We are also using Apache as Webserver with mod.perl. So that is my first question, I don’t see any practical way to combine a WebSocket-Server in that constelation. Maybe there is one I didn’t found yet?

The only thing which really works serious about that topic, is Mojolicious. However I’m not that experienced with that yet, so I’d be happy if someone could state if I can use that in my current mod-perl environment. I think I also would have to let this run as standalone webserver process, No?

Which brings me to my second question. What is the best practice, if you have multiple perl files, which do certain things running on Apache/modperl, but you want to keep all your connected users informed about things. What I mean is, all these scripts are accessed via XHR, but some actions require other users to get informed. Currently, we do a classic ajax polling.

The problem I’m struggling around with is, that if there is a dedicated websocket server, which runs independently, all those scripts would need to somehow communicate with this process as well right ? How would one do that? Pipes? Sockets? Shared memory ?

Theoretically, if I would choose to go with such an independent ws server solution, I could write it in any language right? Could even be Ruby or Node. I’m just wondering if that is the best way or if there is a good solution which is more integrated in existing perl/modperl constructs.

TL;DR

Is it best practice to have a standalone, independent web-socket server which communicates with the rest of your Apache/modperl scripts aswell as with its connected clients ?