Message327648
Exposing internal buffer means committing on a new API contract forever.
I feel a need for reacher read*() API but pretty sure that making internal buffer public is a bad idea. With BufferedProtocol it could be even worse: SLAB allocators can spit a buffer into several separate chunks.
`str.startswith()` supports a tuple of separators, maybe we can do the same for streaming API |
|
Date |
User |
Action |
Args |
2018-10-13 10:21:57 | asvetlov | set | recipients:
+ asvetlov, yselivanov, Bruce Merry |
2018-10-13 10:21:57 | asvetlov | set | messageid: <1539426117.02.0.788709270274.issue32052@psf.upfronthosting.co.za> |
2018-10-13 10:21:57 | asvetlov | link | issue32052 messages |
2018-10-13 10:21:56 | asvetlov | create | |
|