Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ecf-dev] ECF-RFC119 custom discovery provider?

Bryan Hunt wrote:
> Markus,
> 
> I'm looking at the DNS-SD provider, and it appears that only discovery
> and not publish / advertise is supported.  Is that correct.  DNS-SD
> looks promising, but I need both IDiscoveryLocator and
> IDiscoveryAdvertiser.  Any idea on how hard it would be for me to
> implement IDiscoveryAdvertiser?

Advertiser has to be implemented by DNSSec. I'm not sure the DNS
resolver supports DNSSEC. An alternative all this might be to use a
mixture of DNS-SD and SLP which is speced in RFC 3832 [1][2].

> Also, if I'm using an alternate domain, how do I configure the provider
> to use that domain instead of the default host domain?

The idea is that this is done by passing the domain name in the connect
call. However, currently the code always uses my test domain. You'll
have to change the connect() method yourself.

Markus

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=258925
[2] http://www.ietf.org/rfc/rfc3832.txt



Back to the top