From 6a1f339ff72971c8ac2bda66ee192cebf167f563 Mon Sep 17 00:00:00 2001 From: zobalogh Date: Wed, 29 Oct 2014 08:10:54 -0700 Subject: [PATCH] Updated Input node feature definitions (markdown) --- Input-node-feature-definitions.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/Input-node-feature-definitions.md b/Input-node-feature-definitions.md index be44f2d..5339543 100644 --- a/Input-node-feature-definitions.md +++ b/Input-node-feature-definitions.md @@ -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); -* 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 \ No newline at end of file