From: Gavin Lambert (boost_at_[hidden])
Date: 2019-07-03 02:20:57
Mere moments ago, quoth I:
> On 29/06/2019 12:35, JH wrote:
>> As I described in other emails, when one network interface WiFi
>> failed, the network interface Ethernet takes over, the client
>> application using boost ASIO TCP socket cannot detect the broken of
>> WiFi, it continually sent messages to the remote server via the broken
>> WiFi interface without triggering errors but obviously the server
>> could not receive messages any more.
> Receiving on a broken socket reports no errors.Â Trying to send on a
> broken socket, however, should normally return an error code.Â Are you
> sure you're checking in the right places?
Also note that depending on the type of break, it may take a long time
(>=30 seconds in some cases) to get an error when sending.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk