Re: Multi-User DB That Talks to Core Data?
Re: Multi-User DB That Talks to Core Data?
- Subject: Re: Multi-User DB That Talks to Core Data?
- From: Kyle Sluder <email@hidden>
- Date: Fri, 14 Aug 2009 22:41:08 -0700
On Aug 14, 2009, at 9:55 PM, Caleb Strockbine <email@hidden> wrote:
The client gets a bunch of data from the database, turns it into
objects, and stores the objects. Then, at some point later, your
application locates relevant objects from wherever it keeps them,
translates them back into rows of data, and sends them back to the
product database. The fact that the client application happens to
use Core Data to store its objects is really just an implementation
detail that has no bearing on anything outside the client application.
Yes, that would be a way to use Core Data in this context, but I
imagine there would be little advantage. A traditional n-tier model
sounds like it might be better.
Or perhaps maybe Core Data with Sync Services? Sounds like Brad's
company holds "the truth" and periodically gets updates from clients?
That would work out somewhat, and doesn't even involve marshalling
data live over the network, just having Btad's version of the app
opening the persistent store and starting a sync session.
--Kyle Sluder
_______________________________________________
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