I am beginning to step in the unfamiliar area with regard to the executed improvement and made with our RIA (Rich Internet Application) GWT has gone. For people unfamiliar with GWT, essentially when this deployment is done, it is just a pure JavaScript, we are interfering with the server side using XMLHttpRequest using a REST-style XML web service.
Our XML is unearned in Javascript objects and is used within the application to represent the data model behind the interface. When changes occur, the model is updated and returned to XML and sent back to the server.
I have learned the number one performance (in terms of user experience) of performance, as much as possible. Obviously it brings the possibility of caching. Caching is great for static data, but things are difficult in a multi-user system where data on the server can change. Apart from this, the use of "last-modified" and "if-modified-since" requests is not sufficient enough because we want to completely eliminate unnecessary requests.
I want to know that caching data in the browser is right before researching approaches, I hope someone has carried this path forward. I have been searching for such methods, learned lesson, things to avoid etc.
I am happy to provide more specific information when needed ...
In addition, you already have a great advantage with GWT on the traditional HTML app. Unless you are working with special data (i.e.: the fencing is not created very quickly - most reading queries mean) I came to know that there is no special requirement for caching. You're better off service-layer caching because most of the time server-side processing should come. If you can provide more information about the nature of the app, then there may be some different conclusions taken.
Comments
Post a Comment