Gerald Richter wrote:
>
> > - when script changes, AIM should invalidate all cache entries created
> > by that script - one could change color, font etc and AIM should
> > recreate all corresponding images. Maybe script modification time can be
> > added to the hash key?
> >
>
> Also this is possible, it would involve to much overhead, so normaly picture
> serving would slow down.
>
> The easiest solution is to delete all pictures from the cache when you
> change your script. They will be recreated with new script parameter on the
> next request.
OK. May I propose the "NoCache" mode that would be quite usefull for
developing/testing? Something like
SetEnv AIMUseCache No
that would make AIM immediately create a new picture no matter what's
already in the cache? Again, this is of very limited use in the
production server (well, maybe you want to generate images of the map
and "You're here" sign - you don't really want to cache them a lot) but
could still be extremaly usefull for testing and developing when one has
to play with the parameters to find optimal combination etc. (like
'quality' parameter for size vs. quality of JPEG previews)
- Robert
PS Up till now my most common mistake is to forget to set up the
corresponding write permissions to the cache directory. Maybe AIM should
give better warning like die with 'Unable to write to cache' or
something more clear in such cases to give more user-friendly
diagnostics.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
