Updated Input node feature definitions (markdown)

zobalogh 2014-10-29 08:10:54 -07:00
parent 73a7ad4f28
commit 6a1f339ff7
1 changed files with 2 additions and 1 deletions

@ -14,6 +14,7 @@ This page defines the features and design conventions that each input node shoul
### Input nodes SHOULD:
* Have clearly defined behaviour that triggers new msg objects to be sent upon meeting clearly defined conditions
* If a condition forces the node to send multiple messages, they should all be individual msg objects rather than arrays of information
### Input nodes COULD:
* Poll at regular intervals to see if msg trigger conditions are met:
@ -22,5 +23,5 @@ This page defines the features and design conventions that each input node shoul
node.emit("input", {});
}, REPEAT_IN_MILLIS);
</code>
* Alternatively they could fire by being triggered by callbacks => TODO define behaviour here
* Alternatively they could fire by being triggered by callbacks => TODO define behaviour here
* Reserve the right not to send anything at all, ever if conditions are never met