Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Stream early exit #16

kanongil opened this issue Jul 22, 2017 · 2 comments


Copy link

@kanongil kanongil commented Jul 22, 2017

Currently, all bytes of a range stream are processed before signalling 'end'.

Ideally, once the end of the range has been reached ,'end' is signalled, and processing is stopped.

@kanongil kanongil added the feature label Jul 22, 2017

This comment has been minimized.

Copy link

@hueniverse hueniverse commented Oct 30, 2018

I am not following. Can you provide more details?


This comment has been minimized.

Copy link
Member Author

@kanongil kanongil commented Oct 30, 2018

Example: You create a Ammo.Stream() to fetch the first 2 bytes of a source. Then the source provides said 2 bytes, but then stalls. This stall will prevent the Ammo stream from finishing.

Another weirdness, is that post range errors will cause the stream to error, even though all bytes have been delivered.

@hueniverse hueniverse self-assigned this Sep 22, 2019
@hueniverse hueniverse modified the milestones: 3.1.2, 4.0.0 Oct 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
2 participants
You can’t perform that action at this time.