[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Newsgroup Home]
[news.eclipse.technology.riena] Re: Online/Offline Synchronization Workflows

Christian,

I'll do exactly this in my application:

there will be some data normaly not changing about some days-
for these I record in an extra object a version number,
which will be incremented every time data was added, removed,
changed.
a client getting such data also stores the version number
and this data in a local HSQLDB as cache.
at startup from client all versions were checked against the
server and invalid data removed from local cache, so the next
time this data was needed the client will get it fresh from
server.

but as christian said, this is only for data like lists of units,
categories, etc. normaly only 2 - 3 columns in database.

but for the online/offline sync this will be no solution.
I would look to find a good sync-service-solution and then try
to integrate this with Riena

ekke


Christian Campo wrote:

But I certainly can see a point like for pretty simple data objects that
would like to keep a sort
of cache on the client and if you are only you access the server and if not
use the local copy.
For things like country lists, currencies or stuff like that, they dont
change every day or week.