Re caching in the browser, it will depend on both the browser and the http headers that are set in the getImage.cfm request. If you go down the CF serving the images route, ensure that you set appropriate expires headers using cfheader.
Personally, I'd avoid using CF to serve the files. Your requests to the CF Application server will be unnecessarily increased - and CF will always be slower serving that image than would IIS / Apache / CDN. Dominic On 19 October 2011 13:41, JD Yeiter <[email protected]> wrote: > > Can anyone shed some light on this issue for me? I was originally storing > some images in a database, but then I convinced myself that it wasn't the > most efficient way to deliver the images, so I switched my solution to static > files. > > In general, can someone walk me through the pros and cons of placing images > that will be accessed heavily in a database versus keeping them in static > files? What I'm most curious about is: > > 1) When I use a .cfm page in the image tag (< img > src='getImage.cfm?id=282828'/ >), is it cached within browsers just like a > static file? > > 2) Is it too much strain on the database to be constantly requesting 5k - 60k > blobs? > > > Maybe I should just punt and start using Amazon S3? > > -donger > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:348225 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
