As far as I can tell, a simple fix to the std attribute template for ezimage could be done to generate urls like this one:
http://ez.no/site/var/storage/etc.../image.gif?1 where 1 is the version number of the image. As soon as this is done, the webserver can be configured to add expiry headers to image files coming from var/storage that are far away in the future (1year, maybe never), optimizing - user response time - server load Of course this does not apply as easily to ezdesign() tpl operator (but maybe it could, using ?timestamp_of_the_file instead of the version nr). The question is: since the gain is immediate, and this has never been implemented, I wonder if there are known drawbacks / pitfalls in this? Feedback is appreciated Gaetano -- Gaetano Giunta eZ Systems 7 Cité de l'ameublement, 75011 Paris paris : +33 (0)4 78 37 01 33 mobile : +33 (0)6 71 38 78 21 skype : gaetano.giunta http://twitter.com/gggeek -- Sdk-public mailing list [email protected] http://lists.ez.no/mailman/listinfo/sdk-public
