• 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: Sockets and Network Disconnect?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Sockets and Network Disconnect?


  • Subject: Re: Sockets and Network Disconnect?
  • From: Quinn <email@hidden>
  • Date: Fri, 1 Aug 2008 12:52:50 +0100

At 7:36 -0400 1/8/08, Karl Moskowski wrote:
My understanding is that NSOperationQueue gives each NSOperation its own thread automatically. If that doesn't happen, then I can't explain how the UI stays responsive while the NSOperation is active. :)

NSOperationQueue certainly runs the operations on threads. However, the idea is for the operations to do their work and then return, having arranged for the next operation to be started when necessary. That way the system can use a small pool of threads to handle a large number of operations If your operation is blocking on the network, it's subverting that goal.


S+E
--
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


  • Follow-Ups:
    • Re: Sockets and Network Disconnect?
      • From: Jens Alfke <email@hidden>
References: 
 >Re: Sockets and Network Disconnect? (From: Karl Moskowski <email@hidden>)

  • Prev by Date: Re: Sockets and Network Disconnect?
  • Next by Date: Re: Sockets and Network Disconnect?
  • Previous by thread: Re: Sockets and Network Disconnect?
  • Next by thread: Re: Sockets and Network Disconnect?
  • Index(es):
    • Date
    • Thread