Re: Regarding the bonjour services
Re: Regarding the bonjour services
- Subject: Re: Regarding the bonjour services
- From: Chris Parker <email@hidden>
- Date: Wed, 1 Jun 2005 09:54:58 -0700
On Jun 1, 2005, at 5:52 AM, Phill Kelley wrote:
At 12:41 +0530 01/06/2005, KiranKumar wrote:
hi ,
I have a small problem while using the bonjour,in our project
we have client and server applications ,server registers a service
in the local domain,the client is able to resolve the service soon
after it is published,but it is not able to resolve the service if
the server is running from long time and published the service long
time ago,client is able to find the service but not able to resolve
the service.how to solve this problem?
If any one have an idea ,plz respond ASAP.
thanks for reading ,
Are you having a problem under Panther or Tiger?
I am in the middle of developing a bonjour-based app. It all works
perfectly under Panther but everything goes wrong as soon as I add
Tiger to
the mix.
When I trace the callbacks from NSNetService, I see expected
patterns under
Panther like netServiceWillResolve always followed by either
netServiceDidResolveAddress or didNotResolve. Running the same app
on Tiger
I see the netServiceWillResolve but the did/didNotResolve often never
happen. I should make it clear that it is only the Tiger host that
misbehaves. In a mixed Tiger+Panther environment, the Panther hosts
can
still see the Tiger host and resolve it correctly. The actual Tiger
(mis)behavior seems to depend on the order in which the various
bonjour-speaking apps are loaded, whereas with everything running
Panther,
it all just works. I have also tried both the old resolve method
and the
newer resolveWithTimeout method and it makes no difference.
Under Panther, I can't recall seeing a single case where
netServiceDidResolveAddress passed a service where calling the
addresses
method returned an empty array. I see that routinely on Tiger.
Under Panther, I can't recall ever being handed an IPv6 record in an
address structure (call me slack but my pre-Tiger code didn't even
consider
IPv6). Under Tiger, sometimes that is all that I get. And that's
after I've
gone to the trouble of explicitly turning off IPv6 everywhere (no,
I'm not
an IPv6 luddite, I'm simply trying to work out what the heck
bonjour is
trying to do to me).
This is curious, and isn't something I saw in my experience. Do you
have something small you can send me to tinker with that reproduces
the problem?
I stand to be corrected but I've reached the conclusion that
bonjour is
seriously brain-damaged under Tiger, so I'm sticking with Panther
for the
time being.
We've got a couple of NSNetServices and CFNetServices-based fixes in
flight, although I can't talk about when they'll be available...
.chris
--
Chris Parker
Cocoa Frameworks
Apple Computer, Inc.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden