Client ping
Luigi Paioro
luigi at lambrate.inaf.it
Wed Jul 9 01:05:44 PDT 2008
Dear all,
the pre-Trieste working draft foresaw that a callable client had to
implement a samp.client.ping() method (as it still happens for the hub).
In the last draft, this method has been substituted with an
administrative client message "samp.app.ping".
This message could be used by the hub to test whether the registered
callable clients are still alive or died in an unpredictable way. If a
client dies and doesn't respond to a "samp.app.ping" message, then it
can be removed from the list of registered clients.
Anyway a callable client is not supposed to be subscribed to a ping
message and then there can be situations where a callable client which
is not subscribed to a ping message can remain as registered with the
hub forever, even if it died.
A possible way to overcome this problem is the introduction of a
client inactivity timeout, something very similar to the usual
connection or session timeout in the common client/server model. If a
client remains inactive for more that a specified time, then it is
automatically unregistered.
This is applicable to every client, even if they are not callable, so
it is a more general solution respect the ping message test.
What do you think about this proposal?
Regards,
Luigi
More information about the apps-samp
mailing list