That's a good idea unfortunately I also use GWT-RPC calls for authentication and it breaks when using this approach. While I do want to cache the retrieved list, I also want the user to be able to update the list. Caching it might prevent getting the latest copy.
On Wednesday, October 10, 2012 4:33:25 PM UTC+2, Roy wrote: > > An alternative is to make the GWT-RPC request using GET instead of POST, > and have the server return cache headers so the result gets cached in the > browser. I'm doing that in my app - works great. > > Roy > > On Wednesday, October 10, 2012 6:13:20 AM UTC+1, JeanV wrote: >> >> I was wondering if there's anyway to save the returned results from an >> RPC call to an HTML5 enabled browser. Basically the only way I have found >> would be to convert the results into strings and use LocalStorage to save >> them to the browser. I guess my question then would be how can >> IsSerializable java objects be converted to a string and back. >> Any help would be appreciated. >> >> Jean >> >> -- 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/-/RUA4AbsgbwMJ. 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.
