Re: Core Data document-based app design decision?
Re: Core Data document-based app design decision?
- Subject: Re: Core Data document-based app design decision?
- From: Niels Meersschaert <email@hidden>
- Date: Fri, 25 Aug 2006 10:54:07 -0400
Fundamentally, NSUserDefaults and CoreData are two APIs for
persisting data, so either could be appropriate, or you could grow
your own. The real decision should be based on purpose and
performance. If it's preference data, use the NSUserDefaults API as
Uli suggested. If it's a cache of related data, I'd probably suggest
using the CoreData approach, since you can use the SQL datatype which
is much faster than the dictionary key-value xml format of
UserDefaults. The only downside to CoreData is that it is Tiger or
better only, so you do limit your potential customer base. However,
it's a huge development time savings, and from the numbers OmniGroup
reports, most of their customer base is on Tiger anyway.
Good luck,
Niels
On Aug 25, 2006, at 9:46 AM, Uli Kusterer wrote:
Am 25.08.2006 um 11:00 schrieb Jörgen Isaksson:
Is this the correct way to design a Core Data document based
application that needs to save some application related data?
Depends on what the data is. It may be a bit heavyweight if you're
just saving some preferences (i.e. not lots of data but just ten or
so separate small bits). In that case NSUserDefaults and the
NSUserDefaultsController may be a better (non-CoreData) way to save
your application-specific data.
But otherwise I don't see much wrong with this approach. Then
again, I'm not exactly comfortable with CoreData yet, so if someone
else contradicts my assertion, better believe them.
Cheers,
-- M. Uli Kusterer
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden