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

Make Message accept an InputStream instead of an Iterator #9

Merged
merged 1 commit into from
May 15, 2017

Conversation

kelunik
Copy link
Member

@kelunik kelunik commented May 14, 2017

The purpose of Message is to allow streaming and buffering of an InputStream with a simple API. Before this commit, Message served a second purpose: Converting an Amp\Iterator to an InputStream. This has been separated to allow ZlibInputStream and other InputStreams to be used as Message. Converting an Amp\Iterator to an InputStream is now possible using the new IteratorStream class.

The purpose of Message is to allow streaming and buffering of an
InputStream with a simple API. Before this commit, Message served a
second purpose: Converting an Amp\Iterator to an InputStream. This has
been separated to allow ZlibInputStream and other InputStreams to be
used as Message. Converting an Amp\Iterator to an InputStream is now
possible using the new IteratorStream class.
@mention-bot
Copy link

@kelunik, thanks for your PR! By analyzing the history of the files in this pull request, we identified @trowski and @bwoebi to be potential reviewers.

@kelunik kelunik merged commit ad249a8 into master May 15, 2017
@kelunik kelunik deleted the message-input-stream branch May 15, 2017 17:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants