Hi,
Our Core Data point-of-sale app currently shares a sqlite
database on an NAS, each machine periodically fetching fresh
data and, of course, saving. It works well and fast but is
vulnerable to:
network failure,
Apple preventing it (as evidenced briefly in 10.6.2),
sqlite multi-user quirks,
afp quirks
etc...
So, I've begun playing with Sync Services: each machine will
have its own local database store and will do peer and truth
Sync Services syncs.
My question: is that a good idea?
I saw recent wild speculation on Apple's Sync Services mailing
list that Apple may quietly drop Sync Services in Mac OS X
Lion. Also, I'm not clear whether Sync Services was meant to
sync millions of records of a complex schema.
Note that, in the past, many have cheerfully suggested that I
just pop out and roll my own bullet-proof client-server
architecture. I haven't the desire, heart, nor budget for that
garden path. Nor am I convinced its a good idea. Feel free to
address that but I'm more interested in:
So, Sync Services?
Cheers,
Steve
_______________________________________________
Cocoa-dev mailing list ([email protected])
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [email protected]
