-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Connect before bind with inproc #99
Comments
inproc transport should work in the same way as other transports. Would you like to provide a fix? |
Duplicate of issue 6. Closing. |
drahosp
pushed a commit
to LuaDist/libzmq
that referenced
this issue
Feb 13, 2014
Backport for LIBZMQ-541 fix
benjdero
pushed a commit
to benjdero/libzmq
that referenced
this issue
Feb 20, 2023
Fixed examples, and other changes
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For tcp transport, we can connect to endpoint before it is bound. The guide (http://zguide.zeromq.org/chapter:all) says:
"They [connections] exist when a client does zmq_connect(3) to an endpoint, whether or not a server has already done zmq_bind(3) to that endpoint."
However, with inproc transport we must bind before connect, otherwise no connection is created (messages are not delivered). The man (http://api.zeromq.org/zmq_inproc.html) says:
"When connecting a socket to a peer address using zmq_connect() with the inproc transport, the endpoint shall be interpreted as an arbitrary string identifying the name to connect to. The name must have been previously created by assigning it to at least one socket within the same ØMQ context as the socket being connected."
So, some inconsistency exists. I think either guide should be fixed, clearly stating this exception, or (the better choice) - inproc transport should work the same way as tcp.
The text was updated successfully, but these errors were encountered: