[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: {Disarmed} Re: [ecf-dev] avoid broadcast
|
Hi Abhisek,
abhisek saikia wrote:
Hi Scott
Thanks a lot for your response.I completely agree with you for
different behaviour of discovery service.
1) Actually I am confused with why in consumer I am getting same
remote reference add event thrice with different service id.I feel its
a bug.
Please correct me if i am wrong(this is not happening in case of jmdns)
I do think this is wrong, but I can't tell why from your description.
I'm not getting this behavior in my own tests with the hello remote
service and the file-based discovery, so don't believe it's a bug at
this point, but rather something specific to your environment,
configuration or use case. I don't currently have any idea why you are
seeing three published services in your environment, but that's not what
I'm getting in my tests with the hello service and using this product
configuration:
/org.eclipse.ecf.examples.remoteservices.hello.consumer/products/Hello
Service Consumer (localfile,generic).product
If you are seeing something different with the hello examples and this
product configuration (on the consumer) in your environment then it's
possible it's a bug. If that's what you are seeing then please open a
bug and provide a description of how to reproduce the behavior you are
seeing using the code/service that we have access to...i.e. the hello
example...if at all possible.
2)So as per the behavior of file discovery,if my consumer starts
first and my host next,my host services will never be discovered by
the consumer.
Do you mean to handle this i have to make a code dependent on the
discovery api?
Yes...if you you are intent on using the file-based discovery. The
file-based discovery has the default behavior of reading the service
description at startup (which assumes that the remote service is already
available/started). It does not *have* to read the service description
at startup, but if you wish to use the file-based discovery in some
other way (i.e. connect to the remote service at some later point in
time...i.e. defined by you, or initiated upon some event...again defined
by you) then you do need to use not the discovery API, but rather the
file-based discovery provider API...as indicated on the bug.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=305073
Scott
