On Jul 16, 2012, at 2:39 PM, Jens Alfke <j...@mooseyard.com> wrote: > (1) Client-server. The database lives on one server machine, as does the > "business logic" (I hate that term) that manages your app. This could > definitely be implemented with Core Data if you like. The client app just > focuses on the UI, and there is some protocol by which it talks to the server > to fetch data and to tell it to do stuff. In other words, the client app will > not use Core Data.
Another option for client-server is to create an NSIncrementalStore subclass to use on the client, regardless of what you use on the server. The server could be an XML or JSON-based REST web service written using any of a variety of frameworks, the server could be a Mac running a Core Data-based server using a custom protocol you design, the server could be an old mainframe running COBOL... Your NSIncrementalStore subclass can act as an adaptor between it and the rest of your application, allowing your application to be written using Core Data and allowing it to take advantage of its features. -- Chris _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
