A connector router may be used to request it produce a Connector capability. The router may
decide to do so, decline to do so, or return an error, and it may rely on the contents of the
metadata provided when route is called to do so. Routers may also delegate the request to
other routers, often mutating metadata when they do.
A data router may be used to request it produce a Data capability. The router may decide to
do so, decline to do so, or return an error, and it may rely on the contents of the metadata
provided when route is called to do so. Routers may also delegate the request to other
routers, often mutating metadata when they do.
A dictionary router may be used to request it produce a Dictionary capability. The router
may decide to do so, decline to do so, or return an error, and it may rely on the contents of
the metadata provided when route is called to do so. Routers may also delegate the request
to other routers, often mutating metadata when they do.
A dir connector router may be used to request it produce a DirConnector capability. The
router may decide to do so, decline to do so, or return an error, and it may rely on the
contents of the metadata provided when route is called to do so. Routers may also delegate
the request to other routers, often mutating metadata when they do.
An instance token is an opaque identifier tied to a specific component instance. Component
manager relies on these internally to identify which component has initiated a given routing
operation.
A capability is a typed reference to an object owned by component manager. This reference which
may used to interact with the referenced object or this reference may be passed to another
component (or component manager itself).