Re: Notification redundancy
Re: Notification redundancy
- Subject: Re: Notification redundancy
- From: Florent Pillet <email@hidden>
- Date: Thu, 29 Jan 2004 15:36:27 +0100
It seems to me that the various problems you are encountering come from
the sheer number of NSObject instances you are creating in your
product. This certainly sounds more like a design flaw in your
application (you are coding things as if resources were unlimited) than
a flaw in Cocoa.
You may want to rethink your design because that's what is probably
wrong in the first place.
Florent
On 28 janv. 04, at 16:09, Erez Anzel wrote:
If the user changes 50,000 objects in one action, and I use the
"standard" Cocoa approach, then 50,000 notifications are sent to my
registered observer(s), each with its own dictionary attached. (Each
notification comes from the object's primitive "set" method.) Three
views onto the same data means that each notification is observed and
acted upon three times, for a total of 150,000 observations and
reactions. Probably pumps up RAM usage as well, since I can't create
and release my own pool for these notifications; they have to persist
past the time that my action method completes its task.
--
Florent Pillet, Code Segment email@hidden
Developer tools and end-user products for Palm OS & Mac OS X
ICQ: 117292463
http://perso.wanadoo.fr/fpillet
_______________________________________________
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.