Changes between Version 2 and Version 3 of ModuleConfigurationCommunication


Ignore:
Timestamp:
Jan 27, 2010, 1:11:46 AM (8 years ago)
Author:
jelte
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ModuleConfigurationCommunication

    v2 v3  
    1313The data specification is sent to the configuration daemon directly, i.e. in the form of a map containing the single map element "data-specification", as read from the specification file.
    1414
    15 The command to get all configuration for a specific module is { "command": [ "get_config", "<module_name>" ] }, to which the configuration daemon will respond with an answer of the form { "result" : [ 0, <Configuration> ] } or { "result" : [ <status code>, "<error message>" ] }.
     15The command to get all configuration for a specific module is { "command": [ "get_config", { "module_name" : "<module_name>" } ] }, to which the configuration daemon will respond with an answer of the form { "result" : [ 0, <Configuration> ] } or { "result" : [ <status code>, "<error message>" ] }.
    1616
    1717On updates, the configuration manager will send a command to the module of the form { "config_update": <Configuration> }, to which the module will either reply with { "result": [0] } on success, or { "result": [ <status_code>: "<error" ] } if there is an error.