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 -
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
-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
On 11 October 2014 08:10, PJ Eby p...@telecommunity.com wrote:
On Fri, Oct 10, 2014 at 8:56 AM, Graham Dumpleton
graham.dumple...@gmail.com wrote:
So PJE, please step back and do not go rushing out to create a PEP. That is
the worst thing you could do at this point and will only serve to deter
On 11 October 2014 01:56, Graham Dumpleton graham.dumple...@gmail.com wrote:
I've pushed up
https://github.com/python-web-sig/wsgi-ng/commit/df51d7d6fd4faa4efbe397fda2c323932f967020
which hopefully addresses the process and clarity concerns you
expressed. (If not please help me tweak it
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 want to do that).
Did you have any feedback on the proposal
On Fri, Oct 10, 2014 at 9:10 PM, PJ Eby p...@telecommunity.com wrote:
On Fri, Oct 10, 2014 at 8:56 AM, Graham Dumpleton
graham.dumple...@gmail.com wrote:
So PJE, please step back and do not go rushing out to create a PEP. That
is
the worst thing you could do at this point and will only
On 07/10/2014, at 7:15 AM, PJ Eby p...@telecommunity.com wrote:
As before, you can find a living HTML version of the draft in progress at:
https://gist.github.com/pjeby/62e3892cd75257518eb0
(In addition to nice formatting, it also has a clickable table of contents.)
After the next
On 11 October 2014 01:56, Graham Dumpleton graham.dumple...@gmail.com wrote:
...
Robert. What I would suggest you do is reboot this whole effort.
Go back and perhaps look at how the github repo you setup is structured and
make it more obvious how anyone can add their work into it in separate
On Fri, Oct 10, 2014 at 8:56 AM, Graham Dumpleton
graham.dumple...@gmail.com wrote:
So PJE, please step back and do not go rushing out to create a PEP. That is
the worst thing you could do at this point and will only serve to deter
people from the community contributing and so stifle proper
Based on last week's public and private feedback on my native server
APIs pre-PEP, I've done an almost complete rewrite of the previous
draft, in order to provide *concrete examples* of the proposal in use,
along with code samples for Django and WebOb, as well as both HTTP/2
and Websockets.
The
13 matches
Mail list logo