The current architecture is that clients are responsible for connecting to the server [not the other way round]
To ensure there is always a connection to receive screen updates and send keypresses, the client therefore needs to maintain the session. If the client detects the session has failed it tries to reconnect immediately and if it can't it then tries periodically. [nb the player has no notion of off and on - this is all down to the server sending different screen displays] Hence the client needs a way of verifying the connection - this is keepalives for SB2/3 and expecting a periodic screen update for SB1/G players. -- Triode ------------------------------------------------------------------------ Triode's Profile: http://forums.slimdevices.com/member.php?userid=17 View this thread: http://forums.slimdevices.com/showthread.php?t=22789 _______________________________________________ Discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
