I'm in the process of designing an application that will support
syncing and am trying to determine what the best way is to go about
creating the data model. I see that in Leopard, Core Data now has
Sync Services support, allowing "free" syncing if your data model is
based on NSManagedObject and friends. However, the data model for my
application includes relationships with strong ordering which must be
maintained when syncing, and NSManagedObject only supports unordered
relationships.
I know there are ways to "fake" an ordered relationship using Core
Data, usually involving storing an additional attribute in one or more
model objects that keeps track of the ordering. My question is, would
there be any way to use Core Data's built-in Sync Services support
with such a setup, or would I be required (or advised) to do syncing
the "old-fashioned" way if I wanted to support these strongly ordered
relationships?
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Syncservices-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
%(user_optionsurl)s
