On Wed, May 4, 2011 at 9:47 AM, Bob Vawter <[email protected]> wrote:
> > Bob, I've lost track -- are there hooks in place yet that we could > implement > > app specific client side caching in a sample like this? > > You can call RequestFactory.getSerializer() with an implementation of > a ProxyStore (e.g. DefaultProxyStore) in order to indefinitely persist > a proxy. Beyond simple serialization, there's no mechanism in place > to short-circuit requests. > That's proxies. Can requests be serialized? For that matter, any reason not to just hold on to them? I'm not talking about LocalStorage or anything here, just optimizing within a single session. I know we can extend or replace DefaultRequestTransport on the client side, e.g. as done in Expenses for GAE integration<https://cs.corp.google.com/#google3/third_party/java_src/gwt/svn/trunk/samples/expenses/src/main/java/com/google/gwt/sample/gaerequest/client/GaeAuthRequestTransport.java>. If requests have reasonable equality semantics and are somewhat introspectable, even just at the instanceof level, we might be able to get some simple caching done in this sample. @jlabanca, I know your time is short and you gotta do what you gotta do. I don't mean to hold up this change for caching. I just want to have the conversation while we have a use case staring us in the face. > > > -- > Bob Vawter > Google Web Toolkit Team > -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
