Re: CoreData local and on server sync

FROM : Ben Trumbull
DATE : Mon Jun 23 23:03:40 2008

>The way that I did before was, creating my own local database, en then
>when there was a change, replicate the changed data, using DO, to the
>server.
>
>But then I have to keep things in memory.
>
>I was hoping for new ideas or that In the Snow version  was something
>new.
>I guess the way to go is, use a local SQL store with CoreData, and
>replicate the changed data from local to the server using DO.
>The server will also have coredata using SQL.


People have done that.

>But what should I do?
>
>1. The server should have multiply network entries/connections, but
>only one entry to the coredata > SQL


This is a lot simpler, and probably what you want to start with.

>2. The server should have multiply network entries/connections, and
>equal multiply entries to the coredata > SQL <- will coredata keep the
>data uptodate from different read/write requests ( entries) of the
>same data? If f.e one connection do a request for data A and change
>something of data A, that a second connection who want also read Data
>A get the update data?


On 10.5 that's possible, but tricky.  It requires attention to a lot
of details, like staleness intervals, merge policies, and refreshing
objects.
--

-Ben