I agree and I do have pagination where I can possibly do so. The problem arise when I have for example a large form with data that should be populated in or the amount of data I am displaying on one screen itself is big enough e.g. in the case of showing trend data over a period of 4 weeks for example.
On Dec 23, 1:40 pm, "?mit" <uemit.se...@gmail.com> wrote: > Well I agree with mgenov. For tables and lists you should really consider > only transferring data which is actually displayed. > However sometimes this is not possible. > For example in one of my applications I have to display around 50.000 dots > in a 5 different scatterplots. My backend (cherrypy, python webserver) > creates a google visualization datatable (json array) which is passed to my > GWT application. > The response of this json array is around 330 kb in size. It's acutally fast > enough to display it quickly. However by enabling gzip compression on the > webserver I could reduce the response size from 330 kb to around 110 kb. > That's actually quite significant. For these kind of use cases > I definitely recommend to activate gzip compression on the server. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
