-
Notifications
You must be signed in to change notification settings - Fork 25
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
zmq_proxy / ZMQ::Poll in Actor #33
Comments
Its rather straightforward how to do DEALER and ROUTER stuff, made a small gist for it https://gist.github.com/Asmod4n/9372750 /cc @tarcieri |
Thanks for the example, but I cannot see the proxying of the messages from ROUTER to DEALER and back in the example. |
The server(dealer) sends messages to the handler(router), the handler then sends information back and the server reads them. |
I am not quite sure to which ZMQ pattern are you referring to, but I refer to this pattern: http://zguide.zeromq.org/page:all#Shared-Queue-DEALER-and-ROUTER-sockets ROUTER and DEALER are on same node and passing messages internally e.g. proxying I apologize if this was not clear from the issue description. |
The polling is done in the Reactor: https://github.com/celluloid/celluloid-zmq/blob/master/lib/celluloid/zmq/reactor.rb#L13 or do you mean https://github.com/chuckremes/ffi-rzmq/blob/master/lib/ffi-rzmq/device.rb ? @alhafoudh |
As I understand the polling in Reactor is to do the the actor signaling efficient, but I need to make another Poller inside an Actor with two sockets. The DealerSocker and RouterSocket. |
I believe you have to run it in its own actor. At least the specs here do it that way https://github.com/chuckremes/ffi-rzmq/blob/master/spec/device_spec.rb#L30 ^^ |
Yes, but when zmq_proxy is called the program control is never returned and this is a problem for celluloid actors |
@alhafoudh https://github.com/zeromq/czmq will sonnish(i hope) release a 3.0 version of its high level C binding which does this in the background. |
Hi,
how to properly start and handle zmq_proxy or at least ZMQ::Poll?
For example for ROUTER and DEALER socket pair.
The text was updated successfully, but these errors were encountered: