Transmitting that much data will be problematic. I would first seek a way to avoid such transmissions to the client.
But if has to be done this way and all the data should be displayed in single "page", they still should be transmitted in chunks, in size of about what one real client screen would show. When one page is parsed, go fetch next one. If you need it all to make the processing, then you really should do the work on the server. If the parsing of xml can be done with xslt, check that, it might be faster, as browsers do include xslt parsers. Also, if you can target modern browsers, try using workers to do you work on the data. Have You tested how will the browsers behave when feed 1GB xml ? I would prep such file and such big table before going for the actual code... There was a project done in GWT, i believe it's somewhere noted on the webtoolkit homepage, that dealt with huge data sets. It draw a graph of statistical data. Might be useful to see how they handled it. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/5bQZlOxrkoMJ. 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.
