[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [ecf-dev] ECF-RFC119 custom discovery provider?
|
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?
Also, if I'm using an alternate domain, how do I configure the
provider to use that domain instead of the default host domain?
Bryan
On May 21, 2009, at 1:16 AM, Markus Alexander Kuppe wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Bryan Hunt wrote:
I'm now looking at creating a custom discovery provider. My services
will be distributed across a WAN, but I'll have a couple of permanent
servers that can be used for discovery.
Hi Bryan,
you might wanna check out plugins/org.eclipse.ecf.provider.dnssd on
ecf1.osuosl.org (There is also a test project). It's the prototype
of a
DNS-SD based discovery provider. The slides at [1] (p. 64-65) show how
to use it with Bind DNS.
Looking at the JMDNS provider,
I see it contributes three factories:
ecf.discovery.jmdns
ecf.discovery.jmdns.locator
ecf.discovery.jmdns.advertiser
I think I understand the locator and the advertiser ... what's the
third
factory? If I have a service that needs to be discovered, but will
never access any other remote services, do I still need to provide
all
three factories? Also, is extending
AbstractDiscoveryContainerAdapter
the place to start?
The third factory is legacy. Back from the days when there was only
one
class offering both locator and advertiser capabilities. This has
changed in ECF 3.0 though. AbstractDiscoveryContainerAdapter is also a
reminiscence of those days and is likely to be split at some point.
However it's a good start for a custom provider.
Markus
[1] http://ecf2.osuosl.org/Distributed_OSGi_-_The_ECF_way_rev02.pdf
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkoU8cMACgkQH/hL0IhDj1mEsgCgsncFVoVQgAQSSKvSTa8EcCDi
Sg0AoN/J9BtlpgERqASGUS5EwwmbA4Jj
=DLbZ
-----END PGP SIGNATURE-----
_______________________________________________
ecf-dev mailing list
ecf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ecf-dev
