Skip to content

active mode assumes self() should receive all responses #48

okeuday opened this Issue Feb 9, 2013 · 1 comment

1 participant

okeuday commented Feb 9, 2013

Active mode currently assumes that self() during the erlzmq2 function execution is what wants to receive the active mode responses, which is normal based on other Erlang "active" message handling. However, when self() should not receive the responses, it is best to have something like a controlling_process concept (e.g., Erlang sockets). For the erlzmq2 API, an option to socket/2 of "{active_pid, Pid}" makes the most sense, and would then imply "{active, true}". This should help anyone doing active mode erlzmq2 usage for message handling with short-lived processes (due to garbage collection concerns).

@okeuday okeuday referenced this issue Feb 12, 2013

Issue #48 fix #50

okeuday commented Feb 13, 2013

Merged. Thanks!

@okeuday okeuday closed this Feb 13, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.