Re: Core Data Multiple User question
Re: Core Data Multiple User question
- Subject: Re: Core Data Multiple User question
- From: Theodore Petrosky <email@hidden>
- Date: Fri, 24 Jun 2005 04:58:28 -0700 (PDT)
> Message: 10
> Date: Fri, 24 Jun 2005 03:47:36 -0700
> From: Nate Friedman <email@hidden>
> Subject: Core Data Multiple User question
> To: email@hidden
> Message-ID:
>
<email@hidden>
> Content-Type: text/plain; charset="us-ascii"
>
> 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
Nate,
I have been a Postgresql user for about 8 years.
Currently I am working on a job tracking/work tracking
project for an Advertising agency.
If your project is to be multi user, you will need to
use a backend database. I don't think that Core data
helps you here. Although I originally thought that
arrayControllers and object binding wouldn't help
either I recently changed my mind and use them for all
my objects. It is very handy to query the backend and
assign the result to an arraycontroller. then not
worry about the user interface and all the glue code.
My reasons for using postgresql... triggers and
notifications (nested transactions also). My app
allows the users to view 'jobs'. If one of the users
updates the job being view, only the users that are
viewing that job are notified that the row has
changed.
There are pre built binaries available, although I
have always just built the current version (8.0.3).
Good luck.
Ted
__________________________________
Yahoo! Mail Mobile
Take Yahoo! Mail with you! Check email on your mobile phone.
http://mobile.yahoo.com/learn/mail
_______________________________________________
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