From 0cb4ebb18ded8fea425fa60da8596ab5a80b9394 Mon Sep 17 00:00:00 2001 From: zobalogh Date: Wed, 29 Oct 2014 10:08:06 -0700 Subject: [PATCH] Updated Input node feature definitions (markdown) --- Input-node-feature-definitions.md | 1 + 1 file changed, 1 insertion(+) diff --git a/Input-node-feature-definitions.md b/Input-node-feature-definitions.md index 5339543..7c7c180 100644 --- a/Input-node-feature-definitions.md +++ b/Input-node-feature-definitions.md @@ -15,6 +15,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 + * Clean up their state upon close node.on("close", function() {} ### Input nodes COULD: * Poll at regular intervals to see if msg trigger conditions are met: