>>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.
And you are right. The purpose of a database is to store data in some structured way to make possible sorting and searching. If you have nothing to sort or search, the file manager in the operating system is the best you can use. You may have some details about images you can store in the database, ie: title, description, author, etc, but there is nothing to index in the pixels. 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? No, the default headers in all cfm pages prohibit caching. But you can use CF to generate true addresses in the src, if you store images in some directory under the HTTP range. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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:348229 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
