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

Updated Design: Runtime Editor Split (markdown)

Kazuki Nakanishi 2018-03-20 12:47:39 +09:00
parent b6ecfc22a5
commit 55f31963ec
1 changed files with 4 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
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.
</details>