From ea7b71db1bd2188c1bd6694eb5f343d0f9468113 Mon Sep 17 00:00:00 2001 From: Mike Blackstock Date: Tue, 12 May 2015 18:17:09 -0700 Subject: [PATCH] added back my use case around multi-user support --- Design:-Runtime-extension-points.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/Design:-Runtime-extension-points.md b/Design:-Runtime-extension-points.md index 9d9cf9d..6303b7f 100644 --- a/Design:-Runtime-extension-points.md +++ b/Design:-Runtime-extension-points.md @@ -24,6 +24,10 @@ The requirements are: - perform some processing on the flows as part of the deploy process - be able to route messages between the instances are defined by the flow +### Running different flows for different users + +This is the case where different users have access to different node red instances/run times on a single multi-core server or cluster. To do this may require a suitable UI to manage users and instances, a way to broker communications to instances for administration (flow deployment, debugging) and access to flow inputs (e.g. HTTP, web sockets, others) based on user identity and credentials. + ## Extension Points - Storage layer - how/where things get stored - [already done](http://nodered.org/docs/api/storage/index.html).