[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [ecf-dev] ECF ChatClient
|
On 10/09/2013 12:26 PM, Wim Jongman wrote:
> Sending
> 1. The user enters a message
> 2. unregisterOldService()
> 3. publishNewService()
>
> ServiceListener for IChatService
> 1. Receive IChatMessage service REGISTER Event (including my own)
> 2. call getMessage() and put the result on the display
>
> What I see is the following:
>
> * The IChatMessage service REGISTER event is triggered at least twice.
> I guess this is due to the way the service is distributed
What does the service reference look like? Especially the properties are
important. In case of r-OSGi though, two service (proxy) being created
on the remote side is expected. One comes from r-OSGi itself and the
other from ECF remote OSGi.
If you just want to get the service (proxy) registered by ECF remote
services, you will have to filter on the standardized OSGi remote
service properties.
> * The discovery service needs to work hard. Sometimes a client misses a
> registration
>
> * Zoodiscovery breaks contact with the client every xx seconds. On
> reconnect, the service is advertised again.
> This leads to publishing of the same message
Loosing contact to Zoodiscovery happens why? I'm not saying that this
isn't a valid failure mode, but is this due to network problems?
> I guess this pattern needs some additional defensive code to be effective.
I wouldn't expect it to require more defensive coding compared to a pure
non-distributed, yet highly dynamic OSGi runtime environment.
M.
