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

[Phillip J. Eby]

At 11:51 PM 12/18/2007 +0100, Manlio Perillo wrote:
>Phillip J. Eby ha scritto:
>>At 10:10 PM 12/18/2007 +0100, Manlio Perillo wrote:
>>>Ok.
>>>Here I would just say that when someone install something on its 
>>>system, it should at least know what he is doing.
>>And I repeat: you're welcome to your opinions about what's good or 
>>bad, but that has nothing to do with WSGI's design rationale, which 
>>is based on *different* goals.
>
>The problem is that I don't think that having many server 
>configuration parameters with "safe" defaults value is against your 
>design goals.

Sometimes parameters are a necessary evil; that doesn't make them any 
less evil, just more necessary.  :)

However, if they aren't necessary, then they're just plain 
evil.  Range support would be a good example of something where an 
option isn't necessary, since properly-written Range support in the 
server should be able to tell when the application has already 
handled the necessary range-ing of the output.  Thus, having an 
option to turn it on or off is clearly a bad idea, as compared to 
making sure that the Range support is correct in the first place.