From 55f31963ec8c188909edb1497df2328e4ca0080a Mon Sep 17 00:00:00 2001 From: Kazuki Nakanishi Date: Tue, 20 Mar 2018 12:47:39 +0900 Subject: [PATCH] Updated Design: Runtime Editor Split (markdown) --- Design:-Runtime-Editor-Split.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/Design:-Runtime-Editor-Split.md b/Design:-Runtime-Editor-Split.md index 9ae5ceb..642f95e 100644 --- a/Design:-Runtime-Editor-Split.md +++ b/Design:-Runtime-Editor-Split.md @@ -130,4 +130,8 @@ If we stick with a mono-repo, [lerna](https://lernajs.io/) could be used to mana (DCJ) - One of the main items to think about are the UI changes. In the distributed case how is the partitioning of flows done? What attribute says where a particular node should be run? Is it an attribute of a node? Or a group of nodes? or a Tab/Flow? Or should the/a new link node be the thing that distinctly separates parts and holds "location" information for anything it connect to? While distributed and scaled are similar, there is one possible distinction that should be highlighted. For the "simple" scaled case the entire flow is sent to multiple runtimes. Is this worth bringing out separately as this may not need any of these UI changes? + +(KN) - Currently a runtime does not receive user information from editor. +In our past discussion, a runtime needs to receive the information from editor after splitting them. +We may also need to consider the case that both runtime and editor authenticate with different servers.