Re: KVO notifications and threads
Re: KVO notifications and threads
- Subject: Re: KVO notifications and threads
- From: "Hamish Allan" <email@hidden>
- Date: Tue, 15 Jul 2008 22:43:27 +0100
On Tue, Jul 15, 2008 at 7:45 PM, Jerry Isdale <email@hidden> wrote:
> Means we have at least three copies of the data shuffling around memory, but
> hey thats why we buy machines with 2-4 Gb of ram.
If you've got such a large amount of data, it seems unlikely you'd
want to be updating it all during calculations using getters and
setters. Instead, you'd be presenting some sort of aggregate view of
it in your UI; so you'd have one copy of the data and one copy of the
aggregation. They'd both live in the same model, but the code which
performs the aggregation would write its results using
performSelectorOnMainThread:...
1) network receiver captures packets, updates TheModel, possibly
invoking calculation action
2) calculation function does its stuff, updating TheModel
3) aggregation function (in controller) does its stuff, calling
performSelectorOnMainThread:... to update TheModel
4) main thread executes update selector
5) updates trigger KVO of View objects
Hamish
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden