On Fri, 2006-22-12 at 13:26 -0800, Guido van Rossum wrote:
One of the downsides of Python's efficiency is that
it's often easier to code than to reuse!
I was thinking this very same thing earlier this week. This can
sometimes be unfortunate.
- Rocky
--
Rocky Burt
ServerZen Software --
On 12/22/06, Sylvain Hellegouarch [EMAIL PROTECTED] wrote:
We decided to add chunking encoding to our own server, it wasn't all
that hard.
Hopefully you will release this code as part of wsgiref and let the
community benefit from it, right?
We didn't modift wsgiref, we added it to a
On 12/22/06, Sylvain Hellegouarch [EMAIL PROTECTED] wrote:
We decided to add chunking encoding to our own server, it wasn't all
that hard.
Hopefully you will release this code as part of wsgiref and let the
community benefit from it, right?
We didn't modift wsgiref, we added it to a
On 12/22/06, Sylvain Hellegouarch [EMAIL PROTECTED] wrote:
We decided to add chunking encoding to our own server, it wasn't all
that hard.
Hopefully you will release this code as part of wsgiref and let the
community benefit from it, right?
We didn't modift wsgiref, we added it to a
At 09:55 AM 12/22/2006 -0800, Guido van Rossum wrote:
(Also, wsgiref violates a couple of Python style guides that make me
not want to update it myself. Phillip promised he would clean it up
for distribution but never did,
I only have the vaguest recollection of you mentioning this, but can't
Guido,
Getting another piece of open source code added to Google's
infrastructure (and learning how to use it) would have been an order
of magnitude more effort than writing the ~50 lines of code that we
ended up adding.
That's striking. Out of curiosity, can I ask what exactly the
On 12/22/06, Chad Whitacre [EMAIL PROTECTED] wrote:
Getting another piece of open source code added to Google's
infrastructure (and learning how to use it) would have been an order
of magnitude more effort than writing the ~50 lines of code that we
ended up adding.
That's striking. Out
I think I'm done discussing Google internals.
D'oh!
___
Web-SIG mailing list
Web-SIG@python.org
Web SIG: http://www.python.org/sigs/web-sig
Unsubscribe:
http://mail.python.org/mailman/options/web-sig/archive%40mail-archive.com
On 12/20/06, Phillip J. Eby [EMAIL PROTECTED] wrote:
At 12:06 PM 12/20/2006 -0800, Guido van Rossum wrote:
On 12/20/06, Phillip J. Eby [EMAIL PROTECTED] wrote:
At 10:12 AM 12/20/2006 -0800, Guido van Rossum wrote:
We're struggling to use wsgiref behind some Googlish infrastructure,
and one
Sylvain Hellegouarch wrote:
Well, we're using wsgiref's simple_server which only speaks HTTP/1.0,
but we really need to speak HTTP/1.1 and use chunked. Where do you
recommend we put the chunking instead?
shameless-plug
If you are not to fuss about which WSGI server you can afford to use,
Guido,
Well, we're using wsgiref's simple_server which only speaks HTTP/1.0,
but we really need to speak HTTP/1.1 and use chunked. Where do you
recommend we put the chunking instead?
shameless-plug
If you are not to fuss about which WSGI server you can afford to use,
you could grab the
At 08:51 PM 12/20/2006 +, Sylvain Hellegouarch wrote:
[1] http://www.cherrypy.org/browser/trunk/cherrypy/wsgiserver.py
Guido, it does appear that this server implements chunked encoding if you:
1. Use a status of 200, 203, or 206
2. Don't include a Content-Length header
3. *Yield* each
12 matches
Mail list logo
