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: Michael Ash <email@hidden>
- Date: Sat, 16 May 2009 11:09:14 -0400
On Sat, May 16, 2009 at 8:48 AM, Andreas Grosam <email@hidden> wrote:
>>> I really can‘t believe this. It would be a great faux-pas! Do I really
>>> miss
>>> something? Is this limitation anywhere documented?
>>
>> You say "limitation," the rest of the world says "design principle."
>
> A design "principle"? Call it how you like but a database application does
> not have this principle. The opposite is true - it is an anti principle, or
> in other words, any framework that supports any database application shall
> not be single user, single transaction context, non-transactional.
>
> This design "principle" severely limits the number of useful applications.
It also severely limits the design complexity and implementation work.
I really don't understand what the problem is here. CoreData never
claimed to do what you want it to do. It is VERY CLEAR about what it's
for and how it works. Whining about how it doesn't support massive
multi-user applications makes absolutely no sense. You might as well
complain that Cocoa has no support for digital audio processing, or
that your Mac makes a poor platform for embedded computing.
Mike
_______________________________________________
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