Sorry - I made a slightly incorrect statement. GWT 2.0 doesn't eliminate the need to set HTTP cache headers.
If you use ImageBundle ( http://code.google.com/p/google-web-toolkit/wiki/ImageBundleDesign), GWT will bundle multiple images into a single composite image. Also, if your browser supports it, it can inline images using the data:uri<http://en.wikipedia.org/wiki/Data_URI_scheme>format. As a result, the browser is going to make fewer HTTP requests to the server, and on supported browsers - it may not have to make separate requests because the image is already inlined. But you are still going to benefit by setting appropriate cache headers. --Sri 2009/11/14 Vasily Vasilkov <[email protected]> > If you are images are dynamic, or if you are not using GWT 2.0, you will >> have to set appropriate HTTP Cache headers when the image is served. > > > Could you please clarify - what feature I can use in GWT 2.0 instead of > setting http headers? > > -- > 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]<google-web-toolkit%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=. > -- 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=.
