These two terms seem to be used interchangeably. Examples:
Let's, for now, table the relationship between these terms and the "exposed directory"[1], which one could argue deserves another discussion.
Some open discussion:
- An incoming namespace is represented as a list of <path prefix>, <directory handle> pairs, which is used to synthesize what looks like a single directory hierarchy to the component at runtime.
- An outgoing directory / outgoing namespace is an analog: it contains entries that allow the component to synthesize capability handles for others when requested of that component.
The incoming namespace / outgoing directorispace are paired in this way. I propose we rally around one or the other term.
Arguments for "outgoing namespace":
- It makes it clear that it's the analog of "incoming namespace", and in most ways, it is.
Arguments for "outgoing directory":
- It's a single handle, not a list of prefix->handle, like namespace is. Due to this discrepancy in construction, it deserves a different name.
Are there other thoughts? Did I get this wrong and we're about to enter into an "educational moment"?
Gabe
[1] My understanding: a synthesized directory, served by `component_manager` itself, that contains all of the routes in a specific component's .CML with a target of "parent" (== all of the "expose" declarations), regardless of where they are routed from.
--
Gabe Schine
Software Engineer / Manager