On 24 September 2012 19:39, Christian Heimes <christian at python.org> wrote: > Am 24.09.2012 17:27, schrieb Antoine Pitrou: >> >> Hello, >> >> I was wondering if it would be worth providing better HTTP 1.1 support >> in http.server. The way I envision it, there would be a separate >> HTTP11RequestHandler which would provide: >> >> - a smart wfile with automatic chunk encoding (which relieves the API >> user from manually handling chunk encoding or content length >> calculation) >> - keep-alive enabled by default >> - HTTP 1.1 by default (BaseHTTPRequestHandler defaults to 1.0) >> >> What do you think? > > +1 for 3.4 > > You proposed gave me another idea. What do you think about SPDY support > in the stdlib? It's the next step after HTTP 1.1. Given the rate SPDY is changing, complexity of implementation, and that some prerequisites aren't in place (zlib module needs to support specifying the dictionary), this probably isn't a good idea right away. It's also easy to get a similar effect using a SPDY-capable reverse proxy. > > _______________________________________________ > Python-Dev mailing list > Python-Dev at python.org > http://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: http://mail.python.org/mailman/options/python-dev/dw%40botanicus.net
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4