From 57ce74951849f520786b6963622ab35bc2eb8706 Mon Sep 17 00:00:00 2001 From: zobalogh Date: Wed, 29 Oct 2014 10:12:04 -0700 Subject: [PATCH] Updated Output node feature definitions (markdown) --- Output-node-feature-definitions.md | 15 ++++----------- 1 file changed, 4 insertions(+), 11 deletions(-) diff --git a/Output-node-feature-definitions.md b/Output-node-feature-definitions.md index 740f7f5..49cab4f 100644 --- a/Output-node-feature-definitions.md +++ b/Output-node-feature-definitions.md @@ -1,18 +1,11 @@ This page defines the features and design conventions that each output node should adhere to. The page is currently under development and changes to its contents are possible. Once the behaviour is agreed upon, these conventions are going to be migrated onto the Node-RED website for easy reference. -### Putput nodes MUST: +### Output nodes MUST: * Produce a clearly and well defined behaviour that affects some externals outside Node-RED -### Input nodes SHOULD: +### Output nodes SHOULD: * Report errors using node.warn() or node.error() if the external systems are in an unexpected state/behaviour -### Input nodes COULD: -* Poll at regular intervals to see if msg trigger conditions are met: - - node.interval = setInterval(function() { - node.emit("input", {}); - }, REPEAT_IN_MILLIS); - -* 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 +### Output nodes COULD: +* TBC \ No newline at end of file