Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

okeuday opened this issue Feb 9, 2013 · 1 comment


Copy link

@okeuday 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 mentioned this issue Feb 12, 2013
yrashk added a commit that referenced this issue Feb 13, 2013
yrashk added a commit that referenced this issue Feb 13, 2013

This comment has been minimized.

Copy link
Contributor Author

@okeuday 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
None yet
1 participant
You can’t perform that action at this time.