850k is nothing, it's the size of many images or photo's, as hazy1 said, compression will reduce the size dramatically, ( I moved compression from the app server to my fronting Apache and it's much more efficient ) and you can also set the expires header on the GWT html/js to some future date ( a week or month ) ( but do not set it on files that contain .nocache. )
once my app is loaded and cached properly, it's up on the screen with all the required RPC traffic amounting to a a total network xfer of only 4k!!! ( as reported by firebug ) On Nov 13, 2:14 pm, hazy1 <[email protected]> wrote: > Our code size, uncompressed is several megabytes. We compress and > cache it (both on the client and on the server - cache the zipped file > in memory). It is not much trouble after doing this. > > On Nov 12, 6:48 pm, Edgenius <[email protected]> wrote: > > > > > I am very excited for code split feature on Gwt 2.0 as the HTML code > > size after compiled already bloats to 850k. I give a quick try but it > > looks not work like a breeze. I know I have to do more research. I > > don't use lots of third party libraries, actually, only 2 libraries: > > GWT-DND, GWT-LOG. My GWT client code is about 350 classes. > > > So, do you have any good practice to reduce code size? Does code split > > give you very good result? > > > Or just tell us what is your compiled code size and how many your > > classes... -- 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=.
