Can't use two event handlers for two different ports from the same socketio application

[pauloros]

I have a case where I'm expecting two classes of clients to connect to the same socketio application and they would each have their own different messages.

I'm trying to implement this using two different default_http_handlers but socketio_listener:start is giving me the same PID even if I specify different ports in different calls. Subsequently the socketio_listener:event_manager is obviously the same, so if I can't attach different handlers to the two different ports.

From the console:

application:start (misultin).
application:start (socketio).

{ok, Pid1} = socketio_listener:start([{http_port, 8485}, {default_http_handler,h1}]).
{ok, Pid2} = socketio_listener:start([{http_port, 8486}, {default_http_handler,h2}]).

Pid1 == Pid2.
true

Is there a workaround or a better way to achieve this?

[ferd]

Hey there, could you please try my branch at https://github.com/ferd/socket.io-erlang (commit is ferd@a7a1a7c) to see if it works for you?

If it does and you can tell me it's stable enough, I might merge it here.

[pauloros]

Hi, I gave it a quick spin and it seems to work as advertised. I'll split my code in two different handlers to see how it holds the road and will report back.

Thanks for the quick fix!

Paul

[pauloros]

Checking back to report that things appear stable for my own use case, it's been running for a while with the two event managers and everything seems quite fine. Thanks!