On Sat, Sep 27, 2014 at 2:55 PM, PJ Eby p...@telecommunity.com wrote:
On Sat, Sep 27, 2014 at 12:20 AM, Robert Collins
robe...@robertcollins.net wrote:
Right now, anything providing the server profile has to cope with
exceptions and translate those to 500 errors, so we have the variation
of
I am taking full responsibility for this inconsistency. The original
read(n) used stdio's fread(), which reads exactly n bytes or until EOF,
whichever comes first. The switch to 3.0 might have been a good time to fix
this, but we didn't, and now it's too late.
If I had to do it over again I would
I think we're uncovering important assumptions / facts here.
For clarity: I'm not interested in a nice API for HTTP/2. I want
HTTP/2 and its full featureset to be *possible*, *efficient* and
*clear* in a protocol that can replace WSGI - and do so with a fair
chance of adoption. Ditto websockets.
On Sun, 28 Sep 2014 10:43:33 +1300
Robert Collins
robe...@robertcollins.net wrote:
It was in the context of improving streamed unpickling, which is
a problem a bit similar - but less horrible - to JSON unserializing;
since then, the problem was solved in a different way by adding a
