Sim IJskes - QCG wrote:
On 11/07/2010 07:56 AM, Peter Firmstone wrote:
I've been examining the code relating to discovery, feel free to clarify
if I've missed some important detail.
River currently has two discovery protocols,
I assuming you talk about internet deployment here. Assuming the
lowest common denominator here, there is no broadcast on the internet.
Exactly, which is why DNS-SD is attractive (not to be confused with
Multicast DNS), making it possible to discover registrar's in different
domains.
DNS-SD can assist us to discover unknown registrars. DNS-SD would be
used to first discover the host address, port, groups and Service ID of
registrars, then we can use Unicast Discovery to retrieve the lookup
service proxy.
This would be as dynamic on the internet as Multicast Discovery is on
the Intranet today.
Intranet today:
1. Multicast Discovery
2. Using the result from multicast, use unicast to get the registrar
proxy.
The Internet Tomorrow:
1. DNS-SD
2. Using the result from DNS-SD, use unicast to get the registrar proxy.
DNS-SD is something relatively new, which will require support from Bind
etc.
So in order to participate in a specific djinn, you need a
pre-specified registry.
This is currently the situation.
Do you still need discovery in this situation?
No you don't need discovery if you already know your registrar. But
it's no longer dynamic either.
Cheers,
Peter.
