Leopard syncing
Leopard syncing
- Subject: Leopard syncing
- From: Denise Eatherly <email@hidden>
- Date: Wed, 12 Dec 2007 15:28:47 -0700
Hi,
It seemed during the "Tiger era" that we were encouraged to use the
truth database to keep common data types synced ( address book,
calendar, bookmarks, etc), but not our own data types. This made
sense, as we would be storing all the same data twice - once in each
format - not to mention the unknown number of times it would also
exist on additional synced computers. With Leopard, it seems that we
are now being encouraged to use Core Data and the new very handy sync
features to give our apps the ability to use the sync engine and stay
synchronized across multiple machines. This sounds both wonderful
and wasteful. The main question is this -- am I correct about this
interpretation? Are we now encouraged to put copies of our data into
the truth database? Is there no concern that it will become HUGE? I
don't care, if you feel the truth database is set up to handle it.
Also, if we use the truth database to stay synced, how does that work
with 3 computers, say one at home, one at work and a laptop. I'd
like to keep them all synced, so how many copies of the data exist?
Doesn't each machine have a truth database? Whose rules? There is a
mention of designating a "master truth database," but it isn't clear
how you might do that, unless it is just a procedural thing the user
needs to be aware of.
Thanks,
Denise
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden