26 Sep
2013
26 Sep
'13
4:55 p.m.
Peter Dunkley writes:
A good example is that if you are using Amazon Elastic
Load-Balancer to
distribute WebSocket connections, idle connections will be timed-out (by
the Load-Balancer) after 60 seconds - so make sure the server sends
WebSocket pings more frequently than that.
peter,
websocket readme has this:
4.1. keepalive_mechanism (integer)
The keep-alive mechanism to use for WebSocket connections.
Note
If nathelper is only being used for WebSocket connections then nathelper
NAT pinging is not required. If nathelper is used for WebSocket
connections and TCP/TLS aliasing/NAT-traversal then WebSocket
keep-alives are not required.
based on what you write now, is the above readme text still valid, i.e.,
are nat pings enough to prevent amazon load balancer from timing out
websocket connections or are native websocket pings needed instead?
-- juha