You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I have a few processes running, all processes do announce a few services and connect to other services from other processes. To do so I just register a ServiceListener to one or more jmdns instances and wait for services to appear. Most of the time it works flawlessly, but from time to time it happens that one or more services could not be found from one of the processes. Doing some testing with jmdns debug messages enabled I saw that all service details were always received. However for some services the serviceAdded method gets never called instead serviceResolved is called directly.
Now I just wonder if the observer behaviour (serviceResolved called right away without any previous serviceAdded) is intentional?
Regards Michael
The text was updated successfully, but these errors were encountered:
Hi,
I have a few processes running, all processes do announce a few services and connect to other services from other processes. To do so I just register a ServiceListener to one or more jmdns instances and wait for services to appear. Most of the time it works flawlessly, but from time to time it happens that one or more services could not be found from one of the processes. Doing some testing with jmdns debug messages enabled I saw that all service details were always received. However for some services the serviceAdded method gets never called instead serviceResolved is called directly.
Now I just wonder if the observer behaviour (serviceResolved called right away without any previous serviceAdded) is intentional?
Regards Michael
The text was updated successfully, but these errors were encountered: