Resizing Images on-the-fly vs. storing multiple copies on the file system - 09-19-2005 , 09:31 AM
I am working with a web application that allows users to upload high
quality photos into an image library. Those images will then be used in
different places and at displayed at different sizes. My question is,
does anyone know if generating different sizes of the images on-the-fly
would be a big performance hit as opposed to generating several sizes
of each photo as they are uploaded and storing them on the file system.
For example, in the on-the-fly scenario you would just pass different
attributes to a file and it would take the original image that you have
stored and generate the appropriate size, like this.
Any suggestions or opinions would be greatly appreciated.
Re: Resizing Images on-the-fly vs. storing multiple copies on thefile system - 09-19-2005 , 11:45 AM
How about checking to see if the image at the size requested is
available, and if not then converting it and storing it?
Re: Resizing Images on-the-fly vs. storing multiple copies on thefile system - 09-20-2005 , 11:16 AM
this may lead to some security issues. it would be *much* easier for a
haker to do the DOS in this case because of the fact that image
resampling with gdi+ is very resource intense.
|Thread Tools||Search this Thread|