• 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: To thread or not to thread?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: To thread or not to thread?


  • Subject: Re: To thread or not to thread?
  • From: Vincent Lubet <email@hidden>
  • Date: Sun, 16 Feb 2003 15:46:19 -0800

On Sunday, February 16, 2003, at 09:15 AM, Ulrich Bauer wrote:

I have a very general question: I am working on a distributed text editor that currently uses one thread for everything, i.e. one runloop for keyboard events as well as network i/o. Now I've realized that at the moment some runloop modes (selecting text) prevent the network events from getting through and thus the socket buffer may run full.

So what is your opinion: Is it better to introduce a designated thread for handling network events or to try to ensure that no operation or mode blocks the runloop for too much time?

Yes, using a dedicated thread for network operation is necessary in that case.

Vincent
_______________________________________________
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.

  • Follow-Ups:
    • Re: To thread or not to thread?
      • From: Becky Willrich <email@hidden>
References: 
 >To thread or not to thread? (From: Ulrich Bauer <email@hidden>)

  • Prev by Date: Re: WAN address
  • Next by Date: Re: What's possible within a Notifier
  • Previous by thread: To thread or not to thread?
  • Next by thread: Re: To thread or not to thread?
  • Index(es):
    • Date
    • Thread