Message298744
I saw the python-ideas post. I have no experience with http.server, but I just read the doc, and know something of our general enhancement policies. I hope these comments help.
There are two questions: Should compression support be added to http.server? If so, how?
To me, the purpose of the module is to provide a server and request handlers for toy, experimental, and basic production use, whether on a private or the public net. Whatever the case was when the module was written, compression strikes me as a basic http feature now.
I agree with Martin that compression does not fit with the current definition of SimpleHTTPRequestHandler. I suggest instead a subclass thereof. CompressionHTTPRequestHandler? ZippyHTTPRequestHandler? Then add -zip to command line options.
If cgi + compression is relevant, a CompressionMixin might be posible, but I notice that there has been no suggestion so far that the combination is needed.
I suspect one motivation for adding compression to Simple... is to make it default. I understand the desire to give users something for 'free', but changing default behavior usually breaks something somewhere and is therefore contrary to our general policy, and I definitely would not break it for this. |
|
Date |
User |
Action |
Args |
2017-07-20 19:08:29 | terry.reedy | set | recipients:
+ terry.reedy, v+python, r.david.murray, quentel, martin.panter |
2017-07-20 19:08:29 | terry.reedy | set | messageid: <1500577709.74.0.519749561153.issue30576@psf.upfronthosting.co.za> |
2017-07-20 19:08:29 | terry.reedy | link | issue30576 messages |
2017-07-20 19:08:29 | terry.reedy | create | |
|