Re: Multi-User using Core Data?
Re: Multi-User using Core Data?
- Subject: Re: Multi-User using Core Data?
- From: mmalcolm crawford <email@hidden>
- Date: Fri, 10 Jun 2005 02:23:02 -0700
On Jun 10, 2005, at 1:55 AM, Nicko van Someren wrote:
Apple obviously made a conscious decision not to support remote
databases with Core Data - they already had an architecture in
place to do it (EOF), so it clearly could have been done had they
really wanted to. I have no reason if their reason not to include
that support was technical, political, or what, but that being
said, there are a couple of options give use a single data store
for applications on separate machines.
I think that the main reason for not doing this is that CoreData is
essentially free but you have to pay for the Enterprise Objects
framework, so they felt it was necessary to "cripple" the freeware
to a specification that is useful for desktop applications but left
the corporates with deep pockets needing to buy EOF.
Core Data is not a "crippled" EOF. Its goal, and how it contrasts
with EOF, is made clear in the FAQ:
<http://developer.apple.com/documentation/Cocoa/Conceptual/
CoreData/Articles/cdFAQ.html#//apple_ref/doc/uid/TP40001802-244739>
Also note: WebObjects is bundled for free with the Developer Tools...
1) You could make the SQLite data file location a preference
value, and set it to a network drive location.
This is fine until you have two applications accessing the same
data at the same time at which point the memory cache and the file
will get woefully out of sync and "bad things" will happen.
This ("bad things" will happen) is not the case. Just like EOF, Core
Data is designed to properly detect and deal with situations in which
the persistent store is modified by another application, and there
are well-specified patterns to follow if this occurs.
mmalc
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden