[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [ecf-dev] ECF-RFC119 custom discovery provider?
|
Hi Bryan,
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. Looking at the JMDNS
provider, I see it contributes three factories:
ecf.discovery.jmdns
ecf.discovery.jmdns.locator
ecf.discovery.jmdns.advertiser
Yes. Previously there was only one container, that had both the locator
and advertiser. In the 3.0 cycle the locator and advertiser were
separated out, and the combination was left in place (see
https://bugs.eclipse.org/bugs/show_bug.cgi?id=271314).
AbstractDiscoveryContainerAdapter is a good class to start from for a
custom provider.
Markus can also comment on this and other discovery issues as he has
been the lead for working on the discovery API.
Scott
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?
Bryan
_______________________________________________
ecf-dev mailing list
ecf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ecf-dev
