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 Sep 27, 2021. It is now read-only.
I found the example of async rep/req pattern at nanomsg/demo/async_demo.c. In this example, it creates REP socket with with AF_SP_RAW and stores msg_control which is gained from nn_recvmsg. After that, by using nn_sendmsg with stored msg_control, it replies to each associated REQ socket with out of order.
I am a novice about nanomsg, so there can be another implementation of async REP/REQ pattern, but I couldn't find them out.
My hypothesis is that, if you use AF_SP_RAW with the normal messaging APIs, you might not need this handling of the control flag. Maybe you should try that first.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I want to implement async rep/req pattern, but there's no nn_recvmsg/nn_sendmsg supports in nnpy.
In my understanding, async rep/req needs AF_SP_RAW socket and nn_recvmsg/nn_sendmsg with nn_msghdr::msg_control field.
Do you have any plan about supporting nn_recvmsg/nn_sendmsg?
The text was updated successfully, but these errors were encountered: