I have got a little configuration question about this subject:
In Adaptator.xm FMS4 configuration, we can choose a keepalive time for PEERS and SERVER.
I understand the "peers keepalive value", each peer will send a keepalive packet in a corresponding interval, but What does it means a "keepalive server" connection? What is the role of its value?
Thanks again for your job!
both of these times are sent to a client when it connects, commanding it how to handle its different kinds of connections.
the "server keepalive" parameter is the period a client's RTMFP session with the server must be idle before the client sends a keepalive ping.
the "peers keepalive" parameter applies to each of the client's RTMFP sessions with its peers (if any). for each of those sessions, if the session is idle for that long, the client will send a keepalive ping to that peer.
the peers keepalive parameter is typically shorter than the server parameter for three reasons: servers are rarely behind NATs, while it's common for clients to be behind NATs, so P2P connections often need to try harder to keep translations alive; when using RTMFP, the whole point is P2P communication, so more effort should be focused on maintaining those connections; P2P keepalives are distributed while client-server keepalive can focus a lot of traffic in one expensive spot (the server/data center), so client-server keepalive packets should be kept at the minimum that still gets the job done (the "job" being: keep NAT/firewall translations/holes fresh and open, detect client IP address changes, detect connection loss).
Thanks Michael for your detailed response!