• 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: Where is CFStream sources or is CFStream APSL?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Where is CFStream sources or is CFStream APSL?


  • Subject: Re: Where is CFStream sources or is CFStream APSL?
  • From: John Iarocci <email@hidden>
  • Date: Fri, 8 Aug 2003 10:56:28 -0700

On Friday, Aug 8, 2003, at 10:31 US/Pacific, Becky Willrich wrote:

Why do an implementation like CFSocket poll the select() routine instead of
using interrupts by signals?

It's not really polling - CFSocket is blocking in select(). The secondary thread sits idle, blocked in select, until one of the sockets sees some activity, then it kicks out and signals across to the interested thread(s).

If by signals you are referring to BSD signals, the reason we don't use them is because they are not thread-safe (another way to say this is that there is very little you can do reliably in a signal handler).

- John Iarocci
CoreServices, Mgr.
_______________________________________________
macnetworkprog mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/macnetworkprog
Do not post admin requests to the list. They will be ignored.

References: 
 >Re: Where is CFStream sources or is CFStream APSL? (From: Becky Willrich <email@hidden>)

  • Prev by Date: Re: Where is CFStream sources or is CFStream APSL?
  • Next by Date: Locations disappear after creating dialup set with MoreSCF
  • Previous by thread: Re: Where is CFStream sources or is CFStream APSL?
  • Next by thread: Re: Where is CFStream sources or is CFStream APSL?
  • Index(es):
    • Date
    • Thread