Destruction of socket doesn't cancel async operations

[oliora]

ASIO objects like sockets and timers follow the approach that an object destructor cancels all the active async operations with boost::asio::error::operation_aborted error. AZMQ socket doesn't do this, so operation handlers are never called if socket destroyed. I propose to change AZMQ to follow ASIO approach.

[rodgert]

I noticed this when I started refactoring the socket_service and fixed the
behavior in the refactored version. I shelved that to finish the standalone
Asio changes, and due to work constraints I haven't had time to get back to
either set of changes. If it is something pressing, I am happy to take a
fix to the existing code. If we can live with it for a month or so, the
refactored code would include the fix when it is ready.

On Thu, May 14, 2015 at 6:27 AM, Andrey Upadyshev notifications@github.com
wrote:

ASIO objects like sockets and timers follow the approach that object
destructor cancels all the active async operations with
boost::asio::error::operation_aborted error. AZMQ socket doesn't do this,
so operation handlers are never called if socket destroyed. I propose to
change AZMQ to follow ASIO approach.

—
Reply to this email directly or view it on GitHub
#77.

[oliora]

No, it's not pressing. Now we explicitly call cancel() before dtor and everything goes well.