Message325064
Currently, we have separate classes: reader and writer.
It is very inconvenient: these classes are tightly coupled internally, there is no sense to have two objects to the single logical entity.
The second problem is `writer.write()` synchronous API. To support flow control user should call `await writer.drain()` after every `writer.write()` call. But he/she can forget about drain() easy.
`writer.write()` should be softly deprecated in favor of `await writer.send()`. `writer.writelines()` is not very useful, better to merge all buffers before `await stream.send(data)` call. `writelines` should be softly deprecated as well without async replacement.
The last issue is `writer.close()` which should always be used in conjunction with `await writer.wait_closed()`. Let's return a future from `writer.close()`. The encouraged usage becomes `await writer.close()`.
To immediate closing let's add `writer.abort()` sync function which cleans up resources without waiting for actual closing. |
|
Date |
User |
Action |
Args |
2018-09-11 21:18:02 | asvetlov | set | recipients:
+ asvetlov |
2018-09-11 21:18:02 | asvetlov | set | messageid: <1536700682.14.0.0269046726804.issue34634@psf.upfronthosting.co.za> |
2018-09-11 21:18:02 | asvetlov | link | issue34634 messages |
2018-09-11 21:18:02 | asvetlov | create | |
|