[news.eclipse.technology.riena] Re: Online/Offline Synchronization Workf

[Alexander Ziegler <alexander.ziegler@xxxxxxxxxxxx>]

Hi ekke,

I agree that the online/offline sync does not fit well to
your scenario. I understand your needs more like a smart
caching mechanism. There are kind of data exists whose stored
on the server. The client requires these data. The nature of
that data is, that it woulnt change often. Wherefore the is
no need to send this data very time (e.g. If the clients
startup) to the client. A smart caching mechanism could track
this kind of data. If the data becomes changed on the server the caching
mechanism refreshes those data on the client. Is my understanding right?

I also see typical this scenario for key-tables/list types.
But it could also possible that some application will caching
more complex data on the client on a smart way. So I think
that a solution for such smart caching mechanism should open
that the application can define which kind of data and
structures should tracked by a smart caching mechanism. The mechanism maybe
track the data by some strategies, refreshes the data and caches on the
client.

The online/offline sync have a more brighter scoop. In the
offline mode we need  mechanism which stores all needed data
(also high dynamic data) local, so that the user can do the
work / use cases. 

Both mechanism are very interesting for Riena.

Alexander


On 10.04.2008 7:10 Uhr, in article
c93a078ffbd9e1823b8d0e19a288ad08$1@xxxxxxxxxxxxxxx, "ekke"
<ekkehard@xxxxxxxxxxxxxxxxx> wrote:

> 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.
> 
> 
>