Your suggestion is certainly needed on the one hand as making the images no longer viewable on the http server side; but on the other hand, how about the images already downloaded or cached in the browser (for the cache stuff, maybe last modified date can help) But I guess there is really no mechanism to prevent from downloading the images on the user side and then they can spread it as they wish. I just wish I can have a hard cut-off date on the images and after certain days the images themselves can turn into all white pixels or alike.
Thanks for the thought. On 2月18日, 下午7时05分, jchimene <jchim...@gmail.com> wrote: > On Feb 18, 8:44 am, Charlie <xuchangli...@gmail.com> wrote: > > > Sorry for this very off-topic question. But is there any mechanism to > > set up expiration date on image, and after that date the image won't > > be viewable, just like injecting a virus into the image. > > > Or if not image format, is Flash capable of doing that? > > > Thanks for any thoughts, > > Charlie > > The way I've done this in the past is to have a Perl script in a cron > job that sweeps directories and overwrites content with appropriate > "expired" content (.html with such text or .jpg with such content). > The issue is that Apache (or whatever your httpd) needs to be trained > to return other content after the as-of date. That's a bit much to > impose on the httpd server. The replacement text is there to avoid > 404s --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
