On 13 October 2014 16:59, PJ Eby p...@telecommunity.com wrote:
On Sun, Oct 12, 2014 at 6:47 PM, Robert Collins
robe...@robertcollins.net wrote:
FWIW I'm totally fine with you bringing together that PEP - as you say
its complementary to what I'm focused on (I believe I even suggested
you might
On 13 October 2014 17:12, Benoit Chesneau bchesn...@gmail.com wrote:
...
OK,
So I should probably know you, but I can't recollect right now what you do
or write.
Its not clear to me who you were replying to.
If Graham - Graham is the mod_wsgi maintainer, which I'm sure you've
heard of -
One of the issues raised on the github repo was about upgrading to new
protocols. Digging into that I think there is a splinter question: how
*should* we represent the different network protocols in our python
protocol.
I've put some thoughts together about this in
On Mon, Oct 13, 2014 at 11:52 AM, Robert Collins robe...@robertcollins.net
wrote:
On 13 October 2014 17:12, Benoit Chesneau bchesn...@gmail.com wrote:
...
OK,
So I should probably know you, but I can't recollect right now what you
do
or write.
Its not clear to me who you were
On Sun, Oct 12, 2014 at 11:38 PM, Robert Collins robe...@robertcollins.net
wrote:
On 30 September 2014 11:47, Alan Kennedy a...@xhaus.com wrote:
[Robert]
So it sounds like it should be the responsibility of a middleware to
renormalize the environment?
In order for that to be the case,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/13/2014 12:12 AM, Benoit Chesneau wrote:
So I should probably know you, but I can't recollect right now what
you do or write.
Seriously? On *this* sig? PJE was the author of PEP 333, defining the
WSGI 1.0 spec.
Tres.
- --
On 14 October 2014 01:18, Benoit Chesneau bchesn...@gmail.com wrote:
C - Support for chunked uploads, comet, bosh and websockets is
effectively impossible within WSGI - one ends up writing server
specific code, and being tied to a single server - even though
multiple servers support (some
