Actually, I wouldn't mind sending the relevant portion of the
persistent store over the network. The database is an in-house app
that many people will need to be able to work in simultaneously.
We'll use that database to create products and packages and to update
pricing and information. That data needs to be sent to the Core Data
client.
The Core Data-based app is something we'll give to perspective
customers, loading it onto their computer when the time is right.
Only one user at a time will access that software, and we won't need
access to the information until the client is done with it (maybe a
week or two later). Then, we'll import the system they've built back
into the main database app.
So, transfers might happen a few times per month and they can all be
done over a local network.
Making the client app would be much easier using Core Data (and, I've
already actually started working on it).
On Aug 14, 2009, at 10:13 AM, Kyle Sluder wrote:
On Aug 14, 2009, at 10:02 AM, Brad Gibbs <bradgi...@mac.com> wrote:
I'm trying to create a single-user app that uses Core Data, but
gets the data for its object graph from a multi-user database app.
For instance, product information stored in the main database app
could be exported to a catalog in the Core Data-based app. The
user can build a system in the CD-based app and the built system
can be imported back into the main database.
Like I said, you're going to want to look elsewhere. Core Data
doesn't support the pattern you want, unless you're willing to send
the entire persistent store over the network for each read and
write. All custom store types mist be atomic.
You might want to consider using Core Data on the backend and
presenting a custom interface to clients (a la Web Services, or a
RESTful interface). Then if it makes sense the client can use an in-
memory store, hooking into Core Data notifications to perform it's
updates. But at that point you might just want to serialize
NSDictionaries over the wire.
--Kyle Sluder
_______________________________________________
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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
