Note that there are some explanatory texts on larger screens.

plurals
  1. POScaling images stored at S3
    text
    copied!<p>I'm in a situation where I need to push image storage for a number of websites out to a service that can scale indefinitely (S3, CloudFiles, etc.). Up until this point we've been able to allow our users to generate custom thumbnail sizes on the fly using Python's Imaging library with some help from <a href="http://code.google.com/p/sorl-thumbnail/" rel="noreferrer">sorl-thumbnail</a> in Django.</p> <p>By moving our images to something like S3, the ability to <em>quickly</em> create thumbnails on the fly is lost. We can either:</p> <ol> <li>Do it slowly by downloading the source from S3 and creating the thumbnail locally<br> <em>con: it is slow and bandwidth intensive</em></li> <li>Do it upfront by creating a pre-determined set of thumbnail sizes (a'la Flickr) and pushing them all to S3<br> <em>con: it limits the sizes that can be generated and stores lots of files that will never be used</em></li> <li>Let the browser resize using the height/width attributes on the img tag.<br> <em>con: extra bandwidth used by downloading larger than necessary files</em></li> </ol> <p>At this point #3 looks to be a simple solution to the problem with few drawbacks. Some quick tests and <a href="http://www.graphicrating.com/2009/01/03/web-browsers-war-image-rendering/" rel="noreferrer">data from this website</a> show that the quality isn't as bad as expected (we could assure the aspect ratio is maintained).</p> <p>Any suggestions on other options or drawbacks we might not be taking into consideration?</p> <p><em>note: The images are digital photos and are only used for display on the web. Sizes would range from 1000-50 pixels in height/width.</em></p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload