exred_node_redis_daemon v0.2.2 Exred.Node.RedisDaemon
This is a daemon node. It does not handle messages like a regular node. It is used for configuring and starting up a Redis connection pool that other nodes can use.
Link to this section Summary
Functions
Returns a specification to start this module under a supervisor
fire/1 is called when the user clicks on the play button on a node in the UI (and with that triggers a ‘fire’ event). It should return a new_state
handle_msg/2 is called whenever the node receives a message from another node. It should return an {outgoing_msg, new_state} tuple
node_init/1 initializes the node process. This is called as the last step of the node’s init function. Needs to return a new state or a {state, timeout} tuple. (see GenServer documentation)
Link to this section Functions
Returns a specification to start this module under a supervisor.
See Supervisor
.
fire/1 is called when the user clicks on the play button on a node in the UI (and with that triggers a ‘fire’ event). It should return a new_state.
Since this has access to the node’s state it can be used to implement user triggered actions like logging the state, sending messages from the node or creating debug events that are displayed in the debug tab in the UI.
For an example of how to use it see the Trigger node.
Callback implementation for Exred.NodePrototype.fire/1
.
handle_msg/2 is called whenever the node receives a message from another node. It should return an {outgoing_msg, new_state} tuple.
Callback implementation for Exred.NodePrototype.handle_msg/2
.
node_init/1 initializes the node process. This is called as the last step of the node’s init function. Needs to return a new state or a {state, timeout} tuple. (see GenServer documentation)
Callback implementation for Exred.NodePrototype.node_init/1
.