Yeah, this is several white board discussions at least. One last point, though: I think it's perfectly reasonable for find() (or any other read request given domain specific knowledge) to return the latest known proxy rather than force a trip to the server, especially for mobile apps. That's basically the scheme that the AdWords front end has used from early on and it makes a big difference for them (this is public knowledge, fret not). The important thing is to be able to invalidate the cache when some other request notices that that a cached proxy is stale, and to keep a reasonable TTL on the whole thing.
On Wed, May 4, 2011 at 10:16 AM, Bob Vawter <[email protected]> wrote: > On Wed, May 4, 2011 at 1:07 PM, Ray Ryan <[email protected]> wrote: > > Something as simple as short circuiting all equivalent > > RequestFactory.find(EntityProxyId<P>) requests, where equivalent takes > into > > account the proxy version as well as its id, could be very effective. > > Isn't the point of find() to always fetch the latest version? Adding > smarter coalescing makes sense, but I don't think we'd want to squelch > calls to find() completely. How about we pick this discussion up when > we're all in Atlanta? > > -- > Bob Vawter > Google Web Toolkit Team > -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
