I have a question not directly related to the offline functionality.
Is there any good reason to use a UI class (LoadingIndicator) directly in
the OfflineAwareRequestTransport class instead of just using an event
(LoadingIndicatorEvent) on the global event bus and let the application
handle
I've just posted the core part of my offline requestfactory implementation.
http://puretech.siderakis.com/2012/10/offline-requestfactory-gwt.html
Basically all you need to do is extend it and override processPayload (to
save the request payload in local storage), and then send the request
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
On Tuesday, October 9, 2012 9:03:35 AM UTC+2, Christoph Henrici wrote:
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
Am Dienstag, 9. Oktober 2012 12:59:19 UTC+2 schrieb Thomas Broyer:
On Tuesday, October 9, 2012 9:03:35 AM UTC+2, Christoph Henrici wrote:
Best thanx. Szenario 1, would mean that you have to deal with two
different sets of data structures online = entityproxies and offline
something
What be the best approach to develop a offline capable Application using
ReqeustFactory? By Storing Request on locally on the Device and firing
later when online? Or is RequestFactory not recommendable to use, if
offline capability is a requirement?
Best Thanx for any advice.
Christoph
--
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
