• 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: Notification redundancy
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Notification redundancy


  • Subject: Re: Notification redundancy
  • From: Ben Dougall <email@hidden>
  • Date: Thu, 29 Jan 2004 17:38:37 +0000

On Thursday, January 29, 2004, at 04:03 pm, j o a r wrote:

Of course there's a way to get away from that. You can always find an alternative design!
Notifications are not designed to be used like that, and there will surely be
performance issues. Find a way where you don't need notifications - ie. where the objects "know" each other via direct references (ie. pointers).

is using pointers, directly in that manor, even for a fairly small number of objects, to communicate to them when something happens, more efficient than using notifications? it must be. i was thinking, for some reason, there was something more efficient and advantageous (for the computer) in using notifications to send a message to a number of objects, rather than any other way, but on reflection i guess not. hmm :( oh well.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.
  • Follow-Ups:
    • Re: Notification redundancy
      • From: j o a r <email@hidden>
References: 
 >Re: Notification redundancy (From: j o a r <email@hidden>)

  • Prev by Date: Re: Controller binding dies in 2nd NIB
  • Next by Date: Re: Calculating paragraph numbers
  • Previous by thread: Re: Notification redundancy
  • Next by thread: Re: Notification redundancy
  • Index(es):
    • Date
    • Thread