I stop calling async_receive() as soon as I get an error. This works good for TCP sockets.
But with UDP sockets, recvfrom() can return e.g. the error ‘connection refused’ after I called sendto() to a peer machine, where no socket is (yet) bound to the destination port number. So, at least after the error ‘connection
refuxed’, I’d better continue calling async_receive_from().
Are there any recommendations on how to decide, whether the receive callback function should re-initiate a receive operation after a receive error or not?