> this would be like doing exact opposite - put the load of serving > static files onto the already busy DB server
All of your arguments are based on the assumption that files would be served from the database. The only sane environment would be to store the files in the database as a reference but serve them from a filesystem/memcahce/squid cache. Only when the cached resource expires do you make a round-trip to the database again. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
