Re: NSNetwork and NSNetServiceBrowser teardown.
Re: NSNetwork and NSNetServiceBrowser teardown.
- Subject: Re: NSNetwork and NSNetServiceBrowser teardown.
- From: "Quinn \"The Eskimo!\"" <email@hidden>
- Date: Thu, 09 Aug 2012 15:41:39 +0100
On 9 Aug 2012, at 08:03, Kevin Bracey wrote:
> Am I right in assuming, ( it's never right to assuming I know) that once my client and server have got there Streams setup and are ready to communicate that I can stop the NSNetwork and NSNetServiceBrowser.
>
> As I got the Steams from the vended NSService to sure whats needed under the hood.
The general guidelines are:
o Keep the browser running while the service list UI is visible. If the act of connecting hides the service list UI, stop the browser before starting the connect. But if your app's user interface is structured such that connecting doesn't hide the service list, you should leave the browser running to maintain that list.
o Stop the resolve once you've connected. Or, better yet, use a connect-to-service API (-[NSSetService getInputStream:outputStream:] or CFStreamCreatePairWithSocketToNetService) which means you don't have to resolve at all, which means you don't have to stop that resolve (it all happens by magic behind the scenes).
Share and Enjoy
--
Quinn "The Eskimo!" <http://www.apple.com/developer/>
Apple Developer Relations, Developer Technical Support, Core OS/Hardware
_______________________________________________
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