max/notes
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Snapshot

Browse Source
This commit is contained in:
notes 2024-03-21 00:25:00 +00:00
parent 92df421727
commit 9a9f68b9db
2 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
Projects/bachelor/NODE_INTERFACE.md Normal file
View File

@ -0,0 +1 @@
# NODE_INTERFACE

7
Projects/bachelor/Notes.md
View File

@ -4,14 +4,13 @@
We need three major components to work together. I would love it if the node-store and the runtime are super loosely coupled so that they could be replaced by at will. So for example i could use the “server-runtime” that executes the node-graph on the server, or the “local” runtime that executes the node-graph locally.
## [[Projects/bachelor/NODE_INTERFACE]]
This is where the user interacts with the node graph. The frontend loads a node-system. Then fetches all the relevant nodes from the node-store.
This is where the user interacts with the node graph. The frontend loads a node-system. Then fetches all the relevant nodes from the `NODE_REGISTRY`.
## [[Projects/bachelor/NODE_REGISTRY]]
The node-store stores all the nodes. For each node it stores a definition and the wasm blob that executes that node.
The `NODE_REGISTRY` stores all the nodes. For each node it stores a definition and the wasm blob that executes that node.
## [[Projects/bachelor/RUNTIME_EXECUTOR]]
The runtime gets a node-graph and returns the result after executing the node-graph. It fetches the relevant nodes from the node-store.
The runtime gets a node-graph and returns the result after executing the node-graph. It fetches the relevant nodes from the `NODE_REGISTRY`.
This is how these three components would communicate