• 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: Port and runloop problem
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Port and runloop problem


  • Subject: Re: Port and runloop problem
  • From: Markus Hitter <email@hidden>
  • Date: Sun, 26 Aug 2001 12:57:01 +0200

Am Sonntag, 26. August 2001 um 09:08 schrieb Raphael Sebbe:

The problem is that when there are "too many" of these NSPortMessage, some seem to be skipped.

In other words, your "refresh" handling needs more than 50% of the system's performance?

refresh
refresh
(...)
refresh
finished

You might consider just two messages: "startrefresh" and "stoprefresh". This, the port's buffer wouldn't overflow. Between both messages, refresh regularly based on an NSTimer.

Is there a way to tell a message has to be absolutely delivered, or should I use other inter-thread comm technique

Using a NSNotification shouldn't be too complex.

Or your main thread has to acknowledge the message.


Just a few thoughts,
Markus

- - - - - - - - - - - - - - - - - - -
Dipl. Ing. Markus Hitter
http://www.jump-ing.de/


  • Follow-Ups:
    • Re: Port and runloop problem
      • From: Raphael Sebbe <email@hidden>
References: 
 >Port and runloop problem (From: Raphael Sebbe <email@hidden>)

  • Prev by Date: Re: Man cannot rely on headers alone (was Re: Docs)
  • Next by Date: Re: NSTextView
  • Previous by thread: Port and runloop problem
  • Next by thread: Re: Port and runloop problem
  • Index(es):
    • Date
    • Thread