Changes between Version 9 and Version 10 of TrickleApi
- Timestamp:
- Mar 29, 2014, 9:24:54 AM (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TrickleApi
v9 v10 22 22 == Server-side API == 23 23 24 To handle trickle-up messages, use a 'trickle_handler' daemon. This is a program, based on sched/trickle_handler.cpp, linked with a function 24 To handle trickle-up messages, use a 'trickle_handler' daemon. 25 This is a program, based on sched/trickle_handler.cpp, linked with a function 25 26 26 27 {{{ … … 35 36 }}} 36 37 37 This function should return zero if the message was handled successfully; otherwise it will be retried later. The 'hostid' field identifies the host from which the message was sent. The daemon must be passed a '-variety X' command-line argument, telling it what kind of messages to handle. The daemon should be specified in the [ProjectDaemons project configuration file]. 38 This function should return zero if the message was handled successfully. 39 The 'hostid' field identifies the host from which the message was sent. 40 The daemon must be passed a '--variety X' command-line argument, telling it what kind of messages to handle. 41 The daemon should be specified in the [ProjectDaemons project configuration file]. 38 42 39 To send send trickle-down messages (from a trickle handler daemon or other program) you must insert a record in the 'msg_to_host' table. From C/C++, this is done as follows: 43 To send trickle-down messages (from a trickle handler daemon or other program) you must insert a record in the 'msg_to_host' table. 44 From C/C++, this is done as follows: 40 45 41 46 {{{ … … 55 60 }}} 56 61 57 To send trickle-down messages, you mustinclude62 To send trickle-down messages, include 58 63 59 64 {{{