-
Notifications
You must be signed in to change notification settings - Fork 29
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
No pull socket? #5
Comments
Only req, rep, router, dealer, sub and pub are implemented at the moment. Locking at the zeromq docs, it seems that dealer is the closest similar behavior. Could you use that as temporary alternative? BTW: building ezmq_socket_push.erl and ezmq_socket_pull.erl wouldn't take much, but my dev-system is currently down :-( |
Yes, you can use dealer as substitute for pull or push. Dealer is in fact On Sun, Feb 16, 2014 at 3:47 PM, Andreas Schultz
|
Excuse me guys, I couldn't manage to correctly make dealer sends to a pull socket (I'm still quite new to Erlang), would you give me a clue on how to make that work ? :) |
Dealer can send to dealer, it's exactly the same (except biirectional). On Tue, Apr 15, 2014 at 12:56 AM, krakatoa [email protected] wrote:
|
Thanks for the hint Pieter! my problem was on understanding the way to send multiple frames on the ezmq:send/2 function. I got it, and now I'm using a combination of dealer-router, sending data as ezmq:send(Socket, [<<"some-id","","message-here">>]).. |
I try to use a pull socket with ezmq, but I get an error saying there is an error in the socket_type.
escript: exception error: no match of right hand side value {error,invalid_opts}
The text was updated successfully, but these errors were encountered: