NodeDescriptorMapping extension
Translates between OmnyServer's node descriptor and omnyhub's.
omnyhub's descriptor is deliberately thin — an id, a flat capability set,
string labels — because that is all its registry and discovery need to reason
about. OmnyServer's carries a platform profile, structured capabilities and a
content-derived uid, none of which omnyhub has an opinion on. So the full
descriptor travels as JSON in attributes, and the parts omnyhub can use
are mirrored into its own fields so discovery keeps working.
Methods
-
toHub(
) → NodeDescriptor -
Available on NodeDescriptor, provided by the NodeDescriptorMapping extension
The omnyhub descriptor this node advertises at registration.