frodovdr/node-red
1
0
Fork 0
mirror of https://github.com/node-red/node-red.git synced 2023-10-10 13:36:53 +02:00
Code Issues Releases Wiki Activity

Created Query node feature definitions (markdown)

zobalogh 2014-10-29 10:00:40 -07:00
parent 181966bc6f
commit 6c41323cfe
1 changed files with 15 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
Query-node-feature-definitions.md Normal file

@ -0,0 +1,15 @@
This page defines the features and design conventions that each query 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.
### Query nodes MUST:
* Always produce an output msg upon receiving an incoming msg
* Send out a NULL msg.payload if for some reason they cannot provide the appropriate payload (example: data not available yet)
* Upon receiving a NULL message payload, they should.... TODO
### Query nodes SHOULD:
* Have clearly defined behaviour that determines how the incoming msg object is manipulated and then forwarded
* Try to be as stateless as possible (same behaviour regardless of say initialiation properties or any other state)
* MULTIPLE MESSAGE/CLONING BEHAVIOUR TO BE DEFINED
### Query nodes COULD:
* MULTIPLE MESSAGE/CLONING BEHAVIOUR TO BE DEFINED