Performance-wise, a folder on the server is the way to go. - Much less CPU - Server container will automatically handle HTTP caching, meaning once the image is downloaded to the browser's cache, the server will send UNMODIFIED on the next request (unless it's been modified!)
Of course, you could probably code up the 'unmodified' response yourself, but as I understand it, web containers are usually very good at serving resources. Jamie. ----------------------- Find television broadcast antennas in your area (US & Canada): http://www.antennamap.com/ --~--~---------~--~----~------------~-------~--~----~ 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=en -~----------~----~----~----~------~----~------~--~---
