You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 28, 2020. It is now read-only.
Support the zmq_socket_monitored_versioned API to retrieve events for sockets.
My inital idea is to create a unique monitor_addr for each socket. Then we would call zmq_monitor_versioned with this addr to create a ZMQ_PUB monitor socket. The we could create a SocketMonitor which would leverage a ZMQ_SUB and subscribe to the appropriate events. It would then unpack the data into a SocketEvent enum and feed it to a user provided closure. If there is no significant overhead, we should enable that by default.
We could use the same API to create a event logger.
Support the
zmq_socket_monitored_versioned
API to retrieve events for sockets.My inital idea is to create a unique
monitor_addr
for each socket. Then we would callzmq_monitor_versioned
with this addr to create aZMQ_PUB
monitor socket. The we could create aSocketMonitor
which would leverage aZMQ_SUB
and subscribe to the appropriate events. It would then unpack the data into aSocketEvent
enum and feed it to a user provided closure. If there is no significant overhead, we should enable that by default.We could use the same API to create a event logger.
This is required to fix #19.
The text was updated successfully, but these errors were encountered: