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
I have noticed that socket types ZMQ_CLIENT and ZMQ_SERVER have been around since 2016 (version v4.2.0), however they are still only accessible using the DRAFT API. Why has this API not been finalised and what are the blockages to finalise it?
I'm not so interested in those sockets, but I can imagine that there might be more discussion around its API. On the other hand, I'm interested in the socket option ZMQ_NOTIFY_ROUTER which I don't think needs much discussion regarding its API. I'm a bit confused as to why this has not made it into the core codebase? I wouldn't think there would be much API discussion needed to finalise its implementation. I do understand that the actual feature implementation might change or is potentially buggy, but the API shouldn't need much thought.
The text was updated successfully, but these errors were encountered:
I have noticed that socket types
ZMQ_CLIENT
andZMQ_SERVER
have been around since 2016 (versionv4.2.0
), however they are still only accessible using the DRAFT API. Why has this API not been finalised and what are the blockages to finalise it?I'm not so interested in those sockets, but I can imagine that there might be more discussion around its API. On the other hand, I'm interested in the socket option
ZMQ_NOTIFY_ROUTER
which I don't think needs much discussion regarding its API. I'm a bit confused as to why this has not made it into the core codebase? I wouldn't think there would be much API discussion needed to finalise its implementation. I do understand that the actual feature implementation might change or is potentially buggy, but the API shouldn't need much thought.The text was updated successfully, but these errors were encountered: