{"action":"created","issue":{"url":"https://api.github.com/repos/aio-libs/aiohttp/issues/1740","repository_url":"https://api.github.com/repos/aio-libs/aiohttp","labels_url":"https://api.github.com/repos/aio-libs/aiohttp/issues/1740/labels{/name}","comments_url":"https://api.github.com/repos/aio-libs/aiohttp/issues/1740/comments","events_url":"https://api.github.com/repos/aio-libs/aiohttp/issues/1740/events","html_url":"https://github.com/aio-libs/aiohttp/issues/1740","id":215952788,"number":1740,"title":"HTTP pipelining for HTTP-server-side","user":{"login":"socketpair","id":1157412,"avatar_url":"https://avatars2.githubusercontent.com/u/1157412?v=3","gravatar_id":"","url":"https://api.github.com/users/socketpair","html_url":"https://github.com/socketpair","followers_url":"https://api.github.com/users/socketpair/followers","following_url":"https://api.github.com/users/socketpair/following{/other_user}","gists_url":"https://api.github.com/users/socketpair/gists{/gist_id}","starred_url":"https://api.github.com/users/socketpair/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/socketpair/subscriptions","organizations_url":"https://api.github.com/users/socketpair/orgs","repos_url":"https://api.github.com/users/socketpair/repos","events_url":"https://api.github.com/users/socketpair/events{/privacy}","received_events_url":"https://api.github.com/users/socketpair/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2017-03-22T04:55:42Z","updated_at":"2017-03-22T07:55:25Z","closed_at":null,"body":"Does Aiohttp 2.0 support pipelining ? I know, that NGINX HTTP parser supports pipelining. But what about Aiohttp ? Does it handle the case :\r\n\r\n1. Request 1 parsed, and is awaiting it's coroutine A to complete\r\n2. Request 2 parsed, and is awaiting it's coroutine B to complete\r\n3. Coroutine B completed. But it's response must not be written to the connection, until A's response is written.\r\n\r\nIn general, for any TCP-connection (used as HTTP), it is possible to have many coroutines that handle requests simultaneously, and their answers must be strictly ordered. It seems, we should have some queue of responses associated with TCP-connection.\r\n\r\nAlso, we should be able to specify if pipelining should be used. It have many corner-cases which may be not expected. The same for ClientSession. Should it issue piplined requests or not. In both cases pipelining shuold turned off by default (at least for now).\r\n"},"comment":{"url":"https://api.github.com/repos/aio-libs/aiohttp/issues/comments/288323613","html_url":"https://github.com/aio-libs/aiohttp/issues/1740#issuecomment-288323613","issue_url":"https://api.github.com/repos/aio-libs/aiohttp/issues/1740","id":288323613,"user":{"login":"socketpair","id":1157412,"avatar_url":"https://avatars2.githubusercontent.com/u/1157412?v=3","gravatar_id":"","url":"https://api.github.com/users/socketpair","html_url":"https://github.com/socketpair","followers_url":"https://api.github.com/users/socketpair/followers","following_url":"https://api.github.com/users/socketpair/following{/other_user}","gists_url":"https://api.github.com/users/socketpair/gists{/gist_id}","starred_url":"https://api.github.com/users/socketpair/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/socketpair/subscriptions","organizations_url":"https://api.github.com/users/socketpair/orgs","repos_url":"https://api.github.com/users/socketpair/repos","events_url":"https://api.github.com/users/socketpair/events{/privacy}","received_events_url":"https://api.github.com/users/socketpair/received_events","type":"User","site_admin":false},"created_at":"2017-03-22T07:55:25Z","updated_at":"2017-03-22T07:55:25Z","body":"Once again, is aiohttp ready for pipelining even for the case when two (pipelined) responses are streaming writes ?"}}
{"actor":{"display_login":"socketpair"}}