On Jun 9, 2005, at 8:59 AM, J. Scott Anderson wrote:
I am looking for examples/ideas/tips for how to make a Core Data
application multi-user. The idea would be for a common SQLite
database to be accessed by the application from several different
computers. Is this even possible with Core Data today?
In what sense "multi-user"?
If you use the SQLite store, then you can benefit from non-atomic
writes -- that is, a save does not overwrite the whole file -- which
in principle allows multiple users to edit the same store
simultaneously. Core Data uses optimistic locking that can prevent
one user overwriting modifications made by another user, but there is
no "distributed notification" that a value has been changed "under" a
user (you find out at save: time -- see also NSManagedObjectContext's
detectConflictsForObject:). You (obviously) also do not get database
login, row- or table-level locking, or any other related features you
typically associate with a client-server database.
mmalc
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/email@hidden
