-
Notifications
You must be signed in to change notification settings - Fork 150
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
decodeArrayStream vs decodeStream #89
Comments
Those examples look not so good and should be improved. In fact, both can handle chunk of encoded MessagePack binaries, but they handle different formats.
Does it make sense for you? |
Kind of, clarifying that would surely be useful. My question is rather, can I send a stream of individually incomplete chunks?
Can I get this output stream of decoded:
Is this possible? |
Yes, it is possible and the default in all the async or stream decoders. For example, see tests for |
The documentation of
decodeArrayStream
anddecodeStream
is a bit vague, and the signatures and examples are identical.Do we need both? And what's the exact difference? One accepts "an array of items" and the other "independent MessagePack items". Huh?
My exact question is this; Do any of these support byte streams (of arbitrary size) of data consisting of MsgPack items, or do the inputs have to be "complete"?
What I'm explicitly after is support for this:
Is this possible?
The text was updated successfully, but these errors were encountered: