• 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: j o a r <email@hidden>
  • Date: Thu, 29 Jan 2004 17:03:42 +0100

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).

j o a r

On 2004-01-29, at 16.40, Ben Dougall wrote:

> 50,000 notification is 50,000 notifications. if all the objects really
> need to be notified, which i guess they do, otherwise you wouldn't be
> asking the question, then you're going to have to make 50,000
> notifications. i don't think there's any getting away from that.

[demime 0.98b removed an attachment of type application/pkcs7-signature which had a name of smime.p7s]
_______________________________________________
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: Ben Dougall <email@hidden>
References: 
 >Re: Notification redundancy (From: Ben Dougall <email@hidden>)

  • Prev by Date: Re: Notification redundancy
  • Next by Date: building a lazy NSMenu
  • Previous by thread: Re: Notification redundancy
  • Next by thread: Re: Notification redundancy
  • Index(es):
    • Date
    • Thread