Move scout() out of the basic zenoh API #20
Mallets
started this conversation in
Ideas and new features
Replies: 1 comment
-
This idea has been dropped at least for the 0.6.0 release. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Rationale
The scouting protocol is considered to be outside the zenoh protocol itself and it can be implemented via different mechanisms.
E.g., one of those mechanisms could be based on UDP multicast but as well on DNS, LLDP, Bluetooth discovery, IEEE 802.11aq, 3GPP Nnrf_NFDiscovery, etc.
Therefore, zenoh does not require to have scouting in place to work. It's a facilitation for bootstrapping a zenoh system.
To use an analogy, zenoh is IP and scouting is DHCP.
Status quo
Today zenoh scout() API is provided as part of the basic zenoh API.
Currently, scout() is an actual implementation of a discovery mechanism based on UDP multicast.
Nevertheless, scout() is presented as a first citizen API in zenoh.
Proposal
I believe that scout() should be taken out of the basic zenoh API and moved to a module dedicated to scouting in such a way it is made clear that different mechanisms can be used to gather/discover additional information about the zenoh system.
Beta Was this translation helpful? Give feedback.
All reactions