Author asvetlov
Recipients Bruce Merry, asvetlov, yselivanov
Date 2018-10-13.10:21:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
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:57asvetlovsetrecipients: + asvetlov, yselivanov, Bruce Merry
2018-10-13 10:21:57asvetlovsetmessageid: <>
2018-10-13 10:21:57asvetlovlinkissue32052 messages
2018-10-13 10:21:56asvetlovcreate