• 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: Best way to handle background i/o and notify main UI thread
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Best way to handle background i/o and notify main UI thread


  • Subject: Re: Best way to handle background i/o and notify main UI thread
  • From: Douglas Davidson <email@hidden>
  • Date: Tue, 1 Jul 2008 15:17:16 -0700


On Jul 1, 2008, at 3:11 PM, Chris Irvine wrote:

I've been doing a lot of reading about this, but I still don't feel like I have a concise answer. I'm building a small suite of applications that all will all share similar interaction with a UDP based network based peer. It will be necessary to have various background threaded activities to keep the connection alive and monitored. I've already built a small proof of concept using a separate C program that does standard i/o and can be managed by a the Cocoa front end using NSTask. This is somewhat limiting and isn't portable to our most favorite mobile device.

If your need is for the receipt of UDP packets, CFSocket provides a run loop source that can handle that.


Douglas Davidson

_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: Best way to handle background i/o and notify main UI thread
      • From: Chris Irvine <email@hidden>
References: 
 >Best way to handle background i/o and notify main UI thread (From: Chris Irvine <email@hidden>)

  • Prev by Date: Cocoa Programming for Mac OS X (2nd Edition) soultons
  • Next by Date: Re: KVO Bug With Keypaths
  • Previous by thread: Best way to handle background i/o and notify main UI thread
  • Next by thread: Re: Best way to handle background i/o and notify main UI thread
  • Index(es):
    • Date
    • Thread