 |
 |
Hi Fabrizio, thanks for the info. As I say later in my comment, this would indeed help, in the sense that the client would get the response eventually, instead of hanging or crashing, but wouldn't eliminate the real problem: how to handle misbehaving networks. Cheers, Lukasz 2011/3/3 Fabrizio Furano <[log in to unmask]>: > Hi Lukasz, > > something is fishy here: > >> Of course, on every request timeout I could assume that the connection is >> just broken even though the socket is in a valid state and reconnect, no >> problem about that. > > ... in the sense that this is supposed to be the default, normal behavior. > On every request timeout the connection must be considered broken, and > completely wiped out. If it does not do it, then this is the issue to > consider first, imo. > > Fabrizio > >