The GWT application I'm developing (GWT / Spring / Hibernate) returns some large resultsets for the async service requests that feed its pages. Caching these results on the server-side saves me some processing, but I can't avoid the serialization and deserialization required to send it to the UI. From profiling my application, I know that this is the main performance bottleneck right now. So, I'm considering implementing a centralized client-side caching system. I would rather not leave it up to each widget or page to figure out what data to cache and how to cache it - something transparent would be better. The issues I need to deal with are many: handling concurrent async results, keeping the cache size to a maximum so as not to lag the browser, write-through issues, cache invalidation... the list goes on.
Has anybody tried this? How did you do it, and how well did it work? Am I barking up the wrong tree? It sure would be nice if GWT had a standard approach / framework for this. Thanks in advance!
-- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. 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.
