[Web-SIG] serving (potentially large) files through wsgi?

[Phillip J. Eby]

At 07:33 PM 12/17/2007 +0100, Manlio Perillo wrote:
>Ian Bicking ha scritto:
> > [...]
> >
> > The user shouldn't have to anticipate what an application can or should
> > do, beyond what the spec says.
>
>I disagree.
>
>The intent of mod_wsgi for nginx, among other things, is to have an
>"integrated" deployment platform for running WSGI applications;
>so the nginx server configuration *is* the WSGI application configuration.
>
>With mod_wsgi for nginx, you don't run a WSGI application inside the
>nginx server, you just use[1] the nginx server for handling the HTTP
>protocol.
>
>It is a subtle but significative difference, IMHO.

And it's also irrelevant: WSGI applications are composable, which 
means that not only does the application deployer not necessarily 
have any idea what the application does, the *author* might not know 
every detail, either (due to using other libraries, components, and 
middleware).

This is precisely why WSGI doesn't really have any "configuration" 
defined, because the whole idea is that it should be as 
"plug-and-play" as possible.  Server-level configuration options are 
a liability to be avoided, a sometimes-necessary evil.  They aren't a feature.