Coordinator to slave API

From @luca-moser on January 26, 2018 18:50

As the the coordinator's job is to handle the entire configuration for its connected slaves (and their spammers), a set of commands has to be defined which a slave obeys to.

Commands indicating the desired action by the coordinator are handled as byte constants. A command has usually a payload with the argument data.

Note: In the entire setup, the coordinator is able to delegate commands directly to a spammer.

commands (byte constants):

single spammer:

CREATE_SP; creates a new spammer
READ_SP; re-polls data about a spammer's current state
UPDATE_SP; stops the spammer and restarts it with a given configuration
DELETE_SP; removes a given spammer by id
RESTART_SP; restarts a spammer by given id

group:

STOP_SPS: stops all spammers
RESTART_SPS; restarts all spammers
DELETE_SPS: deletes all spammers

A payload can be a spammer's configuration for example, consisting of depth, mwm...parameters.

Copied from original issue: iota-tangle-io/spamalot-project#3

iota-tangle-io / iota-spamalot.go

Coordinator to slave API #1