Correct me if I am wrong but it sounds like your idea will only have one advantage over a traditional caching layer on the server: avoiding serialization costs. You will still have deserialization costs which are likely a lot more time consuming since they happen in javascript in the browser versus in the JVM on the server.
I think what you are suggesting is dangerously bordering along the lines of "ghetto." I feel like caching on the client (using a Command like design pattern and local storage) plus a normal caching layer on the server will vastly outweigh the benefits and hassle of creating and maintaining an GWT-RPC-HTTP frankenstein. -- 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/-/X1X0L3B0JLEJ. 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.
