you couldn't specify a 0 for (local) idleTimeout, so we always flowed
something in our OpenFrame
the client was incorrectly selecting a minimum value between the local
and remote idleTimeouts and then using that as the frequency with
which empty frames should be sent to the server. It should only obey
the remoteIdleTimeout for emitting heartbeats
NB: currently, although we flow an idleTimeout in our OpenFrame, we
don't actually monitor whether or not the remote-end actually sends us
data within this interval, nor do we disconnect them if they don't.
There were a couple of bugs here:
NB: currently, although we flow an idleTimeout in our OpenFrame, we don't actually monitor whether or not the remote-end actually sends us data within this interval, nor do we disconnect them if they don't.