• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Regarding the bonjour services
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Regarding the bonjour services


  • Subject: Re: Regarding the bonjour services
  • From: Marc Krochmal <email@hidden>
  • Date: Wed, 1 Jun 2005 16:17:38 -0700

Hi Phill,

When you say everything goes wrong, is "everything" referring to NSNetService resolve, or is something else going wrong? NSNetService resolve was rewritten in Tiger to be implemented using CFNetServiceResolveWithTimeout, which has different callback behavior than CFNetServiceResolve. If you'd like to get the old behavior, or you need to work around bugs in CFNetServiceResolveWithTimeout, you can temporarily switch to CFNetServiceResolve.

Best Regards,

-Marc


On Jun 1, 2005, at 5:52 AM, Phill Kelley wrote:

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).


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.



Regards, PK _______________________________________________ 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


_______________________________________________ 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
  • Follow-Ups:
    • Re: Regarding the bonjour services
      • From: Phill Kelley <email@hidden>
References: 
 >Regarding the bonjour services (From: KiranKumar <email@hidden>)
 >Re: Regarding the bonjour services (From: Phill Kelley <email@hidden>)

  • Prev by Date: Re: Regarding the bonjour services
  • Next by Date: Temporarily changing DNS servers and search domains in Tiger
  • Previous by thread: Re: Regarding the bonjour services
  • Next by thread: Re: Regarding the bonjour services
  • Index(es):
    • Date
    • Thread