You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is it possible to not use the stream body as an iterator, but to read from it like from a file? I'd like to do read(2048) for example to read the next 2048 bytes.
I skipped around the source a little bit, and it looks like _recv_event is the function that does it, but it has 10000 as a hardcoded read limit.
What do you think about adding to a public function read function to StreamBody?
The text was updated successfully, but these errors were encountered:
On Tue 26 Feb 2019, 7:31 a.m. Hannes Gräuler, ***@***.***> wrote:
Is it possible to not use the stream body as an iterator, but to read from
it like from a file? I'd like to do read(2048) for example to read the
next 2048 bytes.
I skipped around the source a little bit, and it looks like _recv_event
is the function that does it, but it has 10000 as a hardcoded read limit.
What do you think about adding to a public function read function to
StreamBody?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#109>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/ASa9SpPLkLnMIDJR70PrA0s6u7x4zy21ks5vROLrgaJpZM4bRh-6>
.
Is it possible to not use the stream body as an iterator, but to read from it like from a file? I'd like to do
read(2048)
for example to read the next 2048 bytes.I skipped around the source a little bit, and it looks like
_recv_event
is the function that does it, but it has10000
as a hardcoded read limit.What do you think about adding to a public function
read
function toStreamBody
?The text was updated successfully, but these errors were encountered: