Not necessarily so, Ezra. Storing images in the database is perfectly legitimate. However, just like Rails HTML views, you could implement caching of the images on the filesystem (i.e. write them to both the FS and the DB). Whatever action "renders" the image could take care of caching on the FS, serving the FS version if the DB version has, for example, the same MD5 hash as the one in the DB.
Yes, performance will be a bit less than pure FS, but backups are a whole lot simpler (just backup and restore the DB). Besides, servers are cheap compared to developers (just ask the 37s guys), right? == Will Green Find out why this email is 5 sentences or less at http://five.sentec.es/ _______________________________________________ Mongrel-users mailing list Mongrel-users@rubyforge.org http://rubyforge.org/mailman/listinfo/mongrel-users
