Re: Invoice program made in Objective c/Cocoa
Re: Invoice program made in Objective c/Cocoa
- Subject: Re: Invoice program made in Objective c/Cocoa
- From: mmalc Crawford <email@hidden>
- Date: Sun, 17 May 2009 09:45:22 -0700
On May 16, 2009, at 2:48 AM, Andreas Grosam wrote:
(I've never worked with Core Data)
Please do, and then come back with a more informed -- perhaps even
useful -- critique.
Given the complexity of Core Data (and the occasionally interspersed
warnings, that this stuff is no "entry level") it sounds silly that
it would not support database servers, that is, supporting multi-
user, locking and transactions.
So you'd also maintain that it's silly that something that advertises
itself as floor wax isn't also a dessert topping?
Core Data is an object graph management and persistence framework for
desktop applications, not a general ORM tool for client-server programs.
(It does, though, support multi-user access.)
Even more, it would in no way an exaggerated asset if it would
seamlessly support to create application servers, leveraging DO, and
creating web applications with minimal code changes starting from a
single- or a client server model.
If this would be really true, any serious database application could
not use Core Data. So, for what is it anyway? Storing the users
preferences? Creating your own local CD-collection application?
I really can‘t believe this. It would be a great faux-pas! Do I
really miss something?
Yes, you did miss something: The features that Core Data provides to
support desktop applications, including:
• Built-in management of undo and redo beyond basic text editing
• Automatic validation of property values to ensure that individual
values lie within acceptable ranges and that combinations of values
make sense
• Change propagation, including maintaining the consistency of
relationships among objects
• Grouping, filtering, and organizing data in memory and in the user
interface
• Automatic support for storing objects in external data repositories
• Optional integration with Cocoa bindings to support automatic user
interface synchronization
• Automatic support for object faulting, to limit the memory-resident
dataset.
These features are useful for a large proportion of applications,
beyond just those that manage information about CD collections.
As the Core Data team has made clear at successive WWDC presentations,
architecturally it certainly could support client-server databases,
but that's not what would be of most use to the greatest number of
developers in the "short" term. If you would like additional
features, feel free to submit enhancement requests.
Is this limitation anywhere documented?
Yes, in the documentation...
mmalc
_______________________________________________
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