Re: Core Data Multiple User question
Re: Core Data Multiple User question
- Subject: Re: Core Data Multiple User question
- From: SA Dev <email@hidden>
- Date: Fri, 24 Jun 2005 08:20:58 -0400
Hello, Nate:
You may want to search the list archives. It's been discussed (I
think several times) before and the answer was that Core Data is not
intended for multi-user use. Another poster suggested it *could* be
done but would require a lot of hard work (the kind that's way over
*my* head). Hopefully some kind soul will do all of this work and
release it to the public's use and general molestation.
Until then, don't count on Core Data for your particular project.
On Jun 24, 2005, at 6:47 AM, Nate Friedman wrote:
Hello fellow developers,
I've just been recruited to write a data management application to
do inventory management and point of sale for a startup retail
company. I realize that there are probably plenty of apps that
already exist, but the ones that I have experience with using all
suck, so I'm rolling my own for this project - besides, since I'm
one of the owners of this startup, I have the power to say "do it
this way". :)
Right off the bat I want to use Core Data because it looks quite
easy to generate complex applications like this system might
require. My main concern at the moment is how do I allow multiple
workstations to work off of a live single data source.
My first thought was to use file shares (on Mac OS X Server of
course) and point the Core Data Application to have it's data store
on the file share. However my (limited, unresearched) understanding
of SQLLight is that it is only meant for a single process to access
it's data at a time. Would this method work, or would I run into
problems with record keeping as soon as two workstations attempt to
process a sale?
My second thought was to use MySQL (again on Mac OS X Server ;) )
rather than SQLLight, but i haven't read anything about using an
industrial strength database as an alternative to SQLLight/plist.
I'll admit that I haven't done any research in this area, so it
might turn out to be quite easy. As a matter of a fact, this
message is the beginnings of this research.
My third thought was to do a client/server approach, with a custom
Core Data application on my server, and clients that use my own
protocol to access that data. At this point I may as well dump Core
Data all together and find/home grow a MySQL/Cocoa class.
Anyone know the answer to one or both of these problems? Or from a
totally different direction, does anyone know of a good, cheap/free
or even open source POS/Inventory system for the Mac?
Again, this message is my first (baby) steps into both Core Data,
and my research beyond what the sales pitch says. :)
- Nate _______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40silentalcove.net
This email sent to email@hidden
_______________________________________________
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