The best way (in my opinion) to do it is resize one time and save. Hard
drive space is cheaper than a DOS.
If I had one known size, I would agree. But the situation is that I'm
allowing various users to create custom layouts (via the Liquid
template system). I wish to allow all such users to take advantage of
image assets in the system and allow them to request a size that fits
Storage of images will be in the filesystem, and I believe once a given
size has been requested the naming format FlexImage uses supports
caching of that image for future re-use.
> - Don't pass the size in the url, but have keywords or some such that
> relate to a set size. Odds are you dont' really need all the sizes from
> 1x1 to 500x500
Perhaps a workable solution. Instead of allowing users pixel level
control over image size, I could give them increments of 50px to work
with. This way all resizing could be done up front.
> - Pass along an md5 hash that's the combination of the size and some
> secret keyword. Have the fleximage action check it to make sure they
> match. This seems like overkill to me though (just in terms of
Does seem like overkill, but also seems like the one solution offered
so far to allow dynamic resizing from the template which provides some
measure of protection against malicious exploitation. Thanks!
Thanks to everyone so far. If anyone else has two cents to throw in -
please feel free!