2 ms·
Why would your want your app server to serve static content!? Point apache or whatever traditional web server, which is really good at serving static ocntent i
by dkersten 17y ago
Why would your want your app server to serve static content!?
Point apache or whatever traditional web server, which is really good at serving static ocntent in an efficient manner, at it and be done with it.
To answer your question: No, I don't think serving static content should be something your web framework does. It sounds inefficient and less flexible to me. For example, if I have a web server in front of the framework, I have more control over caching and load balancing.
- mattdennewitz 17y agofor local development, i think its perfectly reasonable to assume a built-in development server can handle serving static content. in fact, if it didn't, i'd be a little sour -- it can serve dynamic content, so why not static? and, not everyone wants to run apache or nginx or lighty on their dev machines.