Bryan L. Fordham wrote:
Sure it's useful. It's not unusual at all to have static content served from a server that's designed for that (ie apache) even when you're running a very expensive app server such as weblogic.
<snip>
Okay, I was exaggerating somewhat. But as I see it, there are three basic choices for serving media:
* Configure your webserver so the media is served from a different subdomain, hardcode the domain name into your templates.
* Configure your webserver to run django apps on a different port, again hardcoding the domain name into the templates.
* Create a no-handler location on your webserver, so media doesn't go through the app server.
The first two of these involve including the domain name whenever media is to be inserted onto a page; something that I'm against (mostly because it seems redundant, and if the DN ever changes, finding all the instances would be annoying). The latter works fine, but the django development server has no access to the apache config, nor the media thus.
This has yet to prove to be a big problem for me; and as Jacob pointed out, writing code to display static files can be a nefarious task. So I'll probably just have to live with it.
-Andy
