Changes to NSNetService in Tiger
Changes to NSNetService in Tiger
- Subject: Changes to NSNetService in Tiger
- From: Shane McAliece <email@hidden>
- Date: Mon, 16 May 2005 17:47:40 +0800
Forgive the crosspost to bonjor-dev as well as here, but I thought
perhaps somebody in the larger audience in here would have some
knowledge of my problem,
I'm having some problems with NSNetService and service name collisions
in Tiger. Basically, the name collision functionality is not working any
more more.
Say I open up two copies of my application and use the service name Bob
on the first one, it publishes the service. Then in the second copy I do
the same, using the same service name Bob and publish the service.
Before, in the second copy, it used to correctly notify the delegate and
run the netService:didNotPublish method, as there is a name collision.
It no longer does that. Instead, the netServiceDidPublish delegate is
called, and netService:didNotPublish is never called. I'm sure the
delegate of the service is correctly set, since other delegate methods
are being called, and the service names are the same, the service type
is the same, they are both in the same (default: local.) domain.
The service works correctly if you don't cause a name collision, so the
problem seems isolated to that functionality. I've tried doing the
testing over a network between two computers as well, in case it was
just the behavior when multiple copies run on the same machine. It still
didn't function.
The only thing that no longer works is the netService:didNotPublish
method not being called in a name collision, it just behaves as if there
is no collision.
Does anybody have any ideas why this is? I'm thinking something has
changed in the behavior in Tiger, although it could just be co-incidence
that it happened at the same time. I could find nothing in the
documentation however, apart from a line saying that the
netServiceDidPublish method is new, but errors are still sent to the old
delegate method. The fact that netServiceDidPublish is called, seems to
point to Bonjour not detecting the name collision.
I'd greatly appreciate any suggestions or help with this problem, since
it has me stumped,
Thanks,
Shane McAliece
--
Regards,
Shane McAliece
email@hidden
http://shanemca.shorturl.com/
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden