Need ability to arbitrarily emit with callback to a socket client.

[monteslu]

0.9.x of Socket.io allowed you to get a socket by id and emit to it with a callback such as:

io.sockets.socket(someSocketId).emit('someTopic', data, callback); 

With 1.0.x we can only broadcast to the channel/id of a socket.

[mneil]

I believe you can do this

io.sockets.connected[someSocketId].emit('someTopic', data, callback);

However, I found an issue with callbacks on the client side after 1.0.2

[monteslu]

@mneil awesome!
Not sure if this works across a cluster, but works for a single instance.

[rauchg]

Yup, that's the main reason we did away with the previous public API. That will work on single-node only.

[evanlucas]

Will this work in a cluster if using the redis adapter?

[monteslu]

@evanlucas it still wont. You'll need to handle your own acknowledgments by manually tracking some type of acknowledgment ID tied to a cached callback function. Also, need to make sure you timeout those callbacks and clean up memory in case you never get a response :)

[darrachequesne]

That issue was closed automatically. Please check if your issue is fixed with the latest release, and reopen if needed (with a fiddle reproducing the issue if possible).