I think this makes sense to address - have replied to the ticket. but tl;dr:
inconsistency in this space is likely to provoke bugs, so lets make
things consistent.
-Rob
On 12 May 2014 00:45, mouad ben mouad...@gmail.com wrote:
Hello,
My name is Mouad and this is my first time writing to this
On 19 March 2014 22:02, Tobias Oberstein tobias.oberst...@tavendo.de wrote:
We are working on a system (on top of Autobahn) which provides builtin
scale-up (multi-core) and scale-out (multi-node) capabilities:
https://github.com/crossbario/crossbar
This is work in progress and relies on
https://github.com/python-web-sig/wsgi-ng/issues/4
So doing bidirectional streaming is somewhat incompatible with
requiring that headers be buffered until actual server side content is
available (what if the client is meant to write first... but is itself
waiting for the stream to be
https://github.com/python-web-sig/wsgi-ng/issues/5
tl;dr - we don't specify whether read(size) has to return size bytes
or just not more than size, today. the IO library is clear that
read(n) returns up to n, and also offers read1 that guarantees only
one read call.
I don't think we need read1
