Changes between Version 1 and Version 2 of doc/developer/PingProtocol
- Timestamp:
- 06/25/07 12:42:19 (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
doc/developer/PingProtocol
v1 v2 2 2 3 3 4 Wifidog uses the ping protocol as a heartbeat mechanism to send current status information to the auth server. This enables central logging of the status for each node at the auth server , and perhaps in future two way communications between the auth server and the node to centrally co-ordinate walled-garden settings etc.4 Wifidog uses the ping protocol as a heartbeat mechanism to send current status information to the auth server. This enables central logging of the status for each node at the auth server. 5 5 6 6 The wifidog client uses a setting in the conf file to periodically start a thread ( ping_thread.c ) to send a status message via http to the auth server. The message format is … … 8 8 9 9 {{{ 10 http://auth_sever/ping/ index.php?10 http://auth_sever/ping/? 11 11 gw_id=%s 12 12 sys_uptime=%lu … … 25 25 "\r\n", 26 26 }}} 27 27 28 A typical url would be: /ping/?gw_id=001217DA42D2&sys_uptime=742725&sys_memfree=2604&sys_load=0.03&wifidog_uptime=3861 28 29 29 30 To this the auth server is expected to respond with an http message containing the word "Pong".