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
There should be a way to close a socket (i.e. cancel all async operations and cleanup all resources associated with it, especially ZMQ socket) without calling a destructor. This is extremely useful in multi-threaded applications which tend to spread shared pointers. In such scenario, user has no simple control over socket object lifetime but may need to close it at exact point.
This story is somehow related to #77.
The text was updated successfully, but these errors were encountered:
There should be a way to close a socket (i.e. cancel all async operations and cleanup all resources associated with it, especially ZMQ socket) without calling a destructor. This is extremely useful in multi-threaded applications which tend to spread shared pointers. In such scenario, user has no simple control over socket object lifetime but may need to close it at exact point.
This story is somehow related to #77.
The text was updated successfully, but these errors were encountered: