Client side caching in GWT

Posted by Silfverstrom on Stack Overflow See other posts from Stack Overflow or by Silfverstrom
Published on 2010-03-02T11:05:47Z Indexed on 2010/03/09 4:21 UTC
Read the original article Hit count: 685

Filed under:
|
|
|

We have a gwt-client, which recieves quite a lot of data from our servers. Logically, i want to cache the data on the client side, sparing the server from unnecessary requests.

As of today i have let it up to my models to handle the caching of data, which doesn't scale very well. It's also become a problem since different developers in our team develop their own "caching" functionality, which floods the project with duplications.

I'm thinking about how one could implement a "single point of entry", that handles all the caching, leaving the models clueless about how the caching is handled.

Does anyone have any experience with client side caching in GWT? Is there a standard approach that can be implemented?

© Stack Overflow or respective owner

Related posts about gwt

Related posts about best-practice