You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using my debugger I confirmed that self._options was being set to the above object. Then, in transportwebsocket.js I noted that the options.autoping_interval and options.autoping_timeout values were not defined and that they were set to the defaults of 10 seconds and 5 seconds respectively.
To test this out, I turned off WiFi on my computer, to simulate a situation where the Heartbeat should notice when the network failed. Rather than taking 200 seconds to notice the connection had died, the onclose handler was being called after 15 seconds with reason === 'lost'.
Environment:
Autobahn Version: Tested on 20.4.1, and 18.10.2
Node: 10.16.0
The text was updated successfully, but these errors were encountered:
Summary:
I noted that it appears that
options.autoping_interval
andoptions.autoping_timeout
are not being set inwebsocket.js
.Reproduction:
This was noticed when I was setting up a simple implementation of Autobahn. I provided the following arguments to autobahn.Connection:
Using my debugger I confirmed that
self._options
was being set to the above object. Then, intransportwebsocket.js
I noted that theoptions.autoping_interval
andoptions.autoping_timeout
values were not defined and that they were set to the defaults of 10 seconds and 5 seconds respectively.To test this out, I turned off WiFi on my computer, to simulate a situation where the Heartbeat should notice when the network failed. Rather than taking 200 seconds to notice the connection had died, the
onclose
handler was being called after 15 seconds withreason === 'lost'
.Environment:
Autobahn Version: Tested on
20.4.1
, and18.10.2
Node:
10.16.0
The text was updated successfully, but these errors were encountered: