[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [ecf-dev] question about service discovery ui
|
<stuff deleted>
The reason the Discovery UI uses the CompositeDiscoveryContainer is to
support running multiple real discovery containers simultaneously. If
two or more service ids returned by those containers are equal, they get
combined into one. Since IServiceID is supposed to abstract away the
specific provider, this should work right away.
Hmm. I'm only using the zeroconf/jmdns provider (along with the
Composite Discovery Container), and so I would expect the IServiceID
impl for that provider to filter this out. But apparently it's not.
Strange.
<Scott does tracing and debugging of the service discovery/endpoint
location>
...I see that that my expectation articulated above is wrong...i.e. that
clients that respond to all discovery containers...e.g. jmdns +
composite + etc will be notified of a single service discovery by each
locator, and it's up to them to test for the same serviceID and ignore
all but the one of them (typically the first).
I think what I will do is modify the RSA discovery to deal with this
situation appropriately with new bug [1].
Now a second (design) question: For the new Remote Services
perspective, would people prefer that the Service Discovery view be
added to the Remote Services perspective by default?
Scott
[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=464454
