One alternative for serialization would be to work with AutoBeans. - Advantage: They can be decoded from/encoded to Strings via AutoBeanCodex<http://code.google.com/p/google-web-toolkit/wiki/AutoBean#AutoBeanCodex> .
- Disadvantage: AutoBeans (or the interfaces they represent) can't be used as parameter types for GWT-RPC, so you'd have to convert them to Strings here, too. So effectively you lose type safety. On the upside, AutoBeanCodex can also be used on the server side, so it's easy to en-/decode between AutoBeans and Strings on both sides, and using the same methods for your cache. On Wednesday, October 10, 2012 7:13:20 AM UTC+2, 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/-/AE2R-ThQtsQJ. 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.
