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/-/UIJTO1znFncJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.