Listen to Rick. And picture in your minds the two very different pipes needed to retrieve, process (or not) and serve, and the mechanisms through which each must pass, and how the system's resources react to each. Think about how database-persisted binary data is physically stored, retrieved, delivered, and converted.
Even systems like SharePoint rely on a combination of disk caching and page output caching after the first retrieval of a page's constituent parts from the database. Database storage is for management convenience only; a sophisticated scheme is employed to get those assets out on disk as regular files and then serve them from there. Respectfully, Adam Phillip Churvis Certified Advanced ColdFusion MX 7 Developer BlueDragon Alliance Founding Committee Get advanced intensive Master-level training in C# & ASP.NET 2.0 for ColdFusion Developers at ProductivityEnhancement.com ----- Original Message ----- From: Rick Root To: CF-Community Sent: Monday, February 19, 2007 10:08 AM Subject: Re: Storing images in DB. It takes almost no work for an HTTP server to serve an image. It takes a LOT of work for an HTTP server to serve a CFM file that pulls an image out of a database, converts it to some friendly format and uses cfcontent to push it out. A LOT OF WORK. There are certainly cases where storing an image in the database isn't a bad thing. SERVING it on the fly from the database would be, though. If I wanted to store the actual iamges in the DB, I'd still store them out on the file system as well. Rick ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Create robust enterprise, web RIAs. Upgrade & integrate Adobe Coldfusion MX7 with Flex 2 http://www.adobe.com/products/coldfusion/flex2/ Archive: http://www.houseoffusion.com/groups/CF-Community/message.cfm/messageid:228334 Subscription: http://www.houseoffusion.com/groups/CF-Community/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.5
