DataQueue is missing the read(n) method (and some others)

[schmitch]

Currently the python spec says that there are several utilities methods that needs to be implemented: http://legacy.python.org/dev/peps/pep-3156/#servers

One is really important the read(n) method. Also two other methods are missing.
readline() and readexcatly(n) if aiohttp won't cover these method it isn't compatible to 3156 and won't work with a lot of projects.

Edit: Here is the class that misses these methods: https://github.com/KeepSafe/aiohttp/blob/master/aiohttp/parsers.py#L281

[fafhrd91]

Well, aiohttp is not fully wsgi compliant server and it won't. Wsgi spec doesn't say anything about asyncio coroutines. It is possible to make it compliant with readpayload=true parameter, but this is not for production, it reads payload into memory

[schmitch]

I thought it is compatible with pep-3156? But it isn't.
It still says:

http client/server for asyncio (PEP-3156)

[fafhrd91]

Ah, sorry. I thought about wsgi specs.

Intention for DataQueue is different from StreamReader. You can wrap payload into StreamReader very easily.

[fafhrd91]

Regarding compatibility with pep-3156, it says nothing about http. That was one of the reasons why we moved http code from asyncio to separate project.

[schmitch]

I could, but if I wrap them I would need to write my own program.
But what happens if I use gunicorn with django? It will fail horribly.
So only gunicorn could fix this up, or I would need to write my own 'gunicorn'. Best would be to just include that.

Also PEP-3156 says something about http.

A few functions and classes are provided to simplify the writing of basic stream-based clients and servers, such as FTP or HTTP. Thes are:

It is an Interface and Interfaces should be implemented in my eyes. But who cares.

[fafhrd91]

gjango will fail horribly, because it is doesn't work with asyncio. Asyncio doesn't work like gevent, you can not just install aiohttp and make your application asynchronous. For non trivial application you have to rewrite it to use asyncio.

I don't understated "Interface" part of your comment. Could you elaborate.

[fafhrd91]

Won't fix

[benoitc]

@fafhrd91 not sure but why a buffered stream reader could not be used there? if buffer is empty or < n it could eventually claim for more data until eof.

[fafhrd91]

DataQueue is not a bytes stream, it just holds arbitrary objects that parser emits. for example WebSocketParser emits aiohttp.websocket.Message named tuples. if application requires it is very easy to wrap DataQueue into StreamReader.

[benoitc]

@fafhrd91 if it can be done easily, i think it would be good to have it imo :)

[fafhrd91]

sure, if somebody explain how i can do byte streaming on arbitrary objects, like tuples :)

[ludovic-gasc]

From my experience, you can't access to POST variables in a Flask application without a stacktrace with Gunicorn.
No idea to resolve that, but it looses the interest if we can't use main WSGI frameworks with that.

[fafhrd91]

there is a way. we can change "readpayload" to True, then wsgi.input will work as expected. but this will mean that payload gets loaded into memory.

@asvetlov @benoitc thoughts?