>2) You could write a small, headless server application that would
>vend the data to you client applications using Distributed Objects.
I just asked a similar question... and this is the approach I've been
thinking about. I wonder what object(s) should be vended. The
PersistentStoreCoordinator, the ManagedObjectContext, or the
ManagedObjects themselves.
If I send an object to a client when edits it, do those changes get sent
properly to the server? What about undo, is there only one undo manager
per ManagedObjectContext?
>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.
Is there a way to implement this notification and locking?
-Justin
_______________________________________________
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
This email sent to email@hidden
