PULL socket not receiving after reconnecting to ROUTER about jeromq HOT 3 CLOSED

As far as I know reconnecting to ROUTER socket with same identity would not work well in ZMQ.

from jeromq.

Indeed, this is not how ROUTER sockets work. It would require keeping
internal pipes and messages for sockets, which creates memory leaks.

On Mon, Aug 5, 2013 at 5:55 PM, Dongmin Yu [email protected] wrote:

As far as I know reconnecting to ROUTER socket with same identity would
not work well in ZMQ.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/79#issuecomment-22115746
.

from jeromq.

Ok, so that explains my issue. But for async IM/chat, clients have to be uniquely addressable, otherwise, how can I route messages to clients if I can't identify them? Is there a more appropriate socket combination to make this work?

Wait a minute, I think I got it. If the chat client provides a random id (instead of static one), or just uses the one provided by ROUTER, I can map userId to the connection id on the server, then route accordingly between chat clients. If the client drops off, it reconnects with a different id which I can track on the server. I believe this is more reasonable, the static identity does not make sense, I get it.

I started a question on SO on this topic in case others had the same issue:
http://stackoverflow.com/q/18048951/791406

from jeromq.