Skip to content
This repository has been archived by the owner on Jul 19, 2023. It is now read-only.

Support for namespaced communication #11

Open
mikabytes opened this issue Apr 15, 2021 · 0 comments
Open

Support for namespaced communication #11

mikabytes opened this issue Apr 15, 2021 · 0 comments
Projects
Milestone

Comments

@mikabytes
Copy link
Collaborator

mikabytes commented Apr 15, 2021

There are several situations where several apps can reside in the same Tiden runtime. These may be developed by separate teams, and even be located in separate repositories. In this scenario it would be nice if the nouns used in communication are namespaced so that collisions won't occur.

A few requirements for this:

  1. Scoping: A namespaced app must be able to communicate with the global scope, and possibly "parent scopes". An idea might be to specify for each app what scopes it should include.
  2. The reverse to [1] must be false. I.e., global scope should not be able to make requests to a child scope.
  3. Shadowing must be dealt with in an apparent manner. I.e. a namespaced scope should never be allowed to use same noun as its parent scopes.
  4. Option to create an anonymous scope. These should be generated at runtime and guaranteed to be unique.

This is a prerequisite for confluence merge based nanos. (edit: name was changed in #1 )

@mikabytes mikabytes added this to the 1.1 milestone Apr 15, 2021
@mikabytes mikabytes added this to To do in Core via automation Apr 15, 2021
@mikabytes mikabytes modified the milestones: Bronze, Iron Sep 13, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
Core
To do
Development

No branches or pull requests

1 participant