• 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: Run Loops and CFMessagePorts
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Run Loops and CFMessagePorts


  • Subject: Re: Run Loops and CFMessagePorts
  • From: Mark Pauley <email@hidden>
  • Date: Tue, 28 Feb 2006 14:18:03 -0800

You might want to take a look at the notify api for darwin. It's a lightweight interprocess signaling service, but I bet it will work for inter-thread signaling too. I think you could either use select to listen to a file handle (which might block) or you could use the mach- port method if you need asynchronous signals.

man notify

(disclaimer)
I'm a noob, so I could be way off base on that one.


_Mark

On Feb 28, 2006, at 12:51 PM, Wayne Anderson wrote:

It is in the context of an application.

BTW, I really don't need to send data in this case. Just a simple signal to the application run loop will do. I'm following the sample code in...
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


References: 
 >Run Loops and CFMessagePorts (From: Wayne Anderson <email@hidden>)
 >Re: Run Loops and CFMessagePorts (From: William Stewart <email@hidden>)
 >Re: Run Loops and CFMessagePorts (From: Wayne Anderson <email@hidden>)

  • Prev by Date: Re: deactivating device for debugging
  • Next by Date: Re: Coreaudio-api Digest, Vol 3, Issue 66
  • Previous by thread: Re: Run Loops and CFMessagePorts
  • Next by thread: Re: Run Loops and CFMessagePorts
  • Index(es):
    • Date
    • Thread