On Jul 1, 2007, at 7:32 PM, Yourch, Chris wrote:
I have a “chat” like app that registers with Bonjour and then browses for other “chat” apps. Any “chat” apps that the browse finds I resolve and set a long-lived query on their TXT record.
When the port changes in a particular “chat” app, I deallocate the registration and then re-register with the new port number. The problem is that all the other “chat” apps still see the old port number. I don’t get any TXT notifications or browse changes to indicate that the port number has changed. How would I know that a port number has changed?
Why would the port number need to change such that you'd be required to unregister and then immediately reregister? The client should always re-resolve the service before connecting to it which will always give you the current port number. As a last resort, you could always have some kind of increasing serial number in the TXT record and when it changes, that means this is a new service.
Best Regards,
-Marc
