Re: Notification redundancy
Re: Notification redundancy
- Subject: Re: Notification redundancy
- From: j o a r <email@hidden>
- Date: Thu, 29 Jan 2004 18:53:52 +0100
Notifications are much more expensive, compared with sending messages
to an object that you already have a pointer to.
This doesn't mean that you should never use notifications. You should
not underestimate the importance of optimizing code to be easy to
understand and maintain. Sometimes it makes perfect sense to create a
design around notifications, sometimes not.
But, as we've seen here, even in the cases where it might make sense,
you sometimes have to choose a different solution for memory / CPU
performance reasons.
j o a r
On 2004-01-29, at 18.38, Ben Dougall wrote:
>
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.
[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.