0

NameOwnerChanged() is not always called (inconsistent behaviour)

asked 2014-04-08 01:14:52 -0800

praetp gravatar image

I am using a BusListener and I was hoping to learn the WKN's of all peers by using NameOwnerChanged().

When the client with the BusListener starts up first and then another peer advertises a WKN X, the client is notified of this. (OK!). However, when the other peer starts up first and advertises its WKN, followed by the client with its BusListener, the latter receives NO NameOwnerChanged(). (NOK!) Not really what one might expect, I believe.

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted
0

answered 2014-04-08 11:02:25 -0800

georgen gravatar image

The NameOwnerChanged signal is only reliable for locally owned names. If the name is on a remote device the name is not exchanged till a session is established.

For tracking names between buses the FoundAdvertisedName and LostAdvertisedName should be used.

edit flag offensive delete publish link more
Login/Signup to Answer

Question Tools

Follow
1 follower

Stats

Asked: 2014-04-08 01:14:52 -0800

Seen: 36 times

Last updated: Apr 08 '14