[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [ecf-dev] ECF-RFC119 custom discovery provider?
|
Markus,
I've looked into DNS-SD a bit more, and I don't think it's going to
work. We don't control our DNS servers, and it doesn't look like
there's an easy way to get the code to use a private DNS server.
I started reading through RFC2608, and it seems that I could simply
use SLP with a statically configured DA. Does this approach seem
reasonable? It seems that I simply need to write my own DA.
Bryan
On May 21, 2009, at 2:33 PM, Markus Alexander Kuppe wrote:
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
_______________________________________________
ecf-dev mailing list
ecf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ecf-dev
