From 02e7ef2fdec0ced15d3d7c70882c881e84e159d6 Mon Sep 17 00:00:00 2001 From: Mike Blackstock Date: Tue, 12 May 2015 18:20:39 -0700 Subject: [PATCH] Updated Design: Runtime extension points (markdown) --- Design:-Runtime-extension-points.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Design:-Runtime-extension-points.md b/Design:-Runtime-extension-points.md index 6303b7f..ca405fe 100644 --- a/Design:-Runtime-extension-points.md +++ b/Design:-Runtime-extension-points.md @@ -26,7 +26,7 @@ The requirements are: ### 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. +Unlike support for multiple users accessing a single instance, 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