Hi Wim, Wim Dumon <wim@...> writes: > The problem is that the browser caches the images - it sees the URL > and then decides that it already downloaded the image.
A savvy friend suggested the same, but also mentioned that one may be able to turn the caching off in the header of the page. Is that an option? > You're right in your solution: the filename must change to force the > browser to download the new file. However, Wt offers a method that is > less intrusive than putting hundreds of files in a temporary > directory. See the documentation of WResource, and more specifically > WFileResource (or WMemoryResource). These resources will change their > URL every time that their contents are changed, and the elements > refering to them (WImage/WAnchor/...) will also automatically be > updated. That sounds perfect. I will look into this. [ Browses ... ] And the usage example seems spot on. I will test that. Thanks for the excellent reply. Cheers, Dirk ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ witty-interest mailing list witty-interest@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/witty-interest
