• 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: NSDistributedNotification and Developer Cooperation.. a request for discussion
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: NSDistributedNotification and Developer Cooperation.. a request for discussion


  • Subject: Re: NSDistributedNotification and Developer Cooperation.. a request for discussion
  • From: j o a r <email@hidden>
  • Date: Thu, 11 Oct 2001 11:18:15 +0200

On Thursday, October 11, 2001, at 12:39 , John C. Randolph wrote:

I wonder: what happens to performance if a notification is *really* big? (E.g, what if the string I post is 20 megs or so?) Also, just how fast can such notifications be sent? (Every half-second? Every 15 milliseconds? I'm sure it would be fast enough for a "real-time" stock ticker, but probably not fast enough for an oscilliscope display of an audio waveform.)

Wouldn't this be dealt with in a "lazy" fashion like the pasteboard - ie. the bulk of the data is actually not transfered until requested by the observers? I have no idea, but it seems a likely implementation?
And if so, then I guess performance would be dependent on the numer of observers, and subject to the same physics as every other IO operation on the computer - ie. it only works as fast as your computer allows for.

j o a r


References: 
 >Re: NSDistributedNotification and Developer Cooperation.. a request for discussion (From: "John C. Randolph" <email@hidden>)

  • Prev by Date: Obj-C Runtimes
  • Next by Date: 10.1 server and routing
  • Previous by thread: Re: NSDistributedNotification and Developer Cooperation.. arequest for discussion
  • Next by thread: Re: half-initialized objects during decoding (Re: Persistance)
  • Index(es):
    • Date
    • Thread