• 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: Network Programming Models (was OTCountFreeBytes?)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Network Programming Models (was OTCountFreeBytes?)


  • Subject: Re: Network Programming Models (was OTCountFreeBytes?)
  • From: Becky Willrich <email@hidden>
  • Date: Mon, 4 Feb 2002 12:19:30 -0800

Is there something wrong with using the timeout parameter to force it to return at regular intervals to pick up your instructions??

Only the CPU spin on the thread, and the difficulty in choosing a reasonable timeout. I must be prepared to block for up to the timeout; if I choose a long timeout, I delay whatever the pending work is by that amount. If I choose a short timeout, I end up consuming CPU spinning in a tight while loop. It's a quite manageable problem (after all, people have been using select quite effectively for years), but personally, I prefer to work off a run loop of some kind.

REW


References: 
 >Re: Network Programming Models (was OTCountFreeBytes?) (From: email@hidden)

  • Prev by Date: Re: Network Programming Models (was OTCountFreeBytes?)
  • Next by Date: Re: Is Open Transport Dying?
  • Previous by thread: Re: Network Programming Models (was OTCountFreeBytes?)
  • Next by thread: Re: Network Programming Models (was OTCountFreeBytes?)
  • Index(es):
    • Date
    • Thread