Re: Core data or else?
Re: Core data or else?
- Subject: Re: Core data or else?
- From: Jens Miltner <email@hidden>
- Date: Tue, 25 Sep 2007 10:16:28 +0200
Am 25.09.2007 um 00:51 schrieb Devraj Mukherjee:
Hi Mike & Jum,
Thanks for your responses. I am writing an application that provides
desktop integration for the Asterisk PBX server
(http://asterisktools.org). One of the features is a "Call Log", so it
keeps a record of Missed, Recd. and Outgoing calls. I am anticipating
it will be 20 entries per list, so about 60 rows which can be cleared
by the user.
The data will be recorded when the call is initiated and will be
displayed on a list at the users request. I really don't anticipate
the lists to grow because of the nature of the application.
What would you suggest I do? Core Data? Or head with an NSDocument
style approach?
First of all, I wouldn't necessarily anticipate the list to remain
small - I'm sure some users will just never clean the list and it
keeps growing... Murphy's law.
This sounds like a good candidate for a CoreData application to me.
It's not really a document bound application (at least not from the
user's perspective, since there's probably not a notion of a document
the user opens - it's more like iTunes: the user starts the
application and a database is opened without the need for the user to
navigate to a document file. Also, it's probably a good idea to
anticipate data growing larger than one may believe is 'useful'.
For an application of this type, I'd go with a CoreData application
with an sqlite backend, storing the data in an application-specific
folder inside Library/Application Support. (which Library folder
depends on whether the app is a system-wide server or a per-user
service).
HTH,
</jum>
Thanks for your time.
PS Should have explained myself better in the first instance :)
On 9/24/07, Jens Miltner <email@hidden> wrote:
Am 24.09.2007 um 13:09 schrieb Devraj Mukherjee:
Hi everyone,
I need to store very little data for an application that I am
writing.
Is a Core Data based approach the best way to go or are there
simpler
ways?
If it's really very little data you need to store, using a property
list to store data may also be sufficient.
However, what the _best_ approach is, really depends on you (and your
application). If writing a CoreData application is easier, you should
go with that. CoreData also lets you choose the backend, but none of
that really adds a lot of overhead if your dataset is small.
If all you need to do is read a piece of data, a plain NSDocument
based application may be just what you need. If your app is a single-
window-type of application, you may not even need a document based
application. Without further information, it's hard to tell which
would be the best application template to use...
If there is a chance that your dataset will become larger in the
future, creating a CoreData application may be the wiser choice.
HTH,
</jum>
_______________________________________________
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