Best thanx. Szenario 1, would mean that you have to deal with two
different sets of data structures online = entityproxies and offline
something else..... or you have to develop your "own" layer above request
factory.... which to avoid was the rational behind using requestfactory.
Szenario 2 seems like a interesting approach, but i must confess i not
knowlegable enough of the internals of Requestfactory to really be able to
see what that means. Also for adressing the issue with the potential
confict resolution this is probably not the "right" layer....
So probably you need something above RequestfFactory, which deals with a
"higher level" batching and offline / online awareness etc.......
Am Montag, 8. Oktober 2012 19:04:10 UTC+2 schrieb Jens:
>
> I think I would store data changes locally and when the device is back
> online I would send everything to the server and let the server synchronize
> it with its server database. The server can send conflicts back to the
> client and then let the user choose which version of the conflicted data
> should be used. So I would not store the specific requests, but only the
> data (along with some meta data like timestamp, isDeleted, etc.).
>
> So its pretty much:
>
> if(online) {
> // requestfactory
> } else {
> // use local data cache
> }
>
> I am not sure if its possible to implement a custom RequestTransport for
> RequestFactory, e.g. OfflineRequestTransport, that parses the RF payload
> and executes/applies all the invocations/operations locally using a local
> data cache. If it would be possible you could switch to an
> OfflineRequestTransport as soon as you are offline and you dont need that
> "if(online)" block everywhere in your code.
>
> -- J.
>
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-web-toolkit/-/HhBDMGHWLNgJ.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
