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

support for chunks #7

Open
4gra opened this issue Apr 27, 2021 · 0 comments
Open

support for chunks #7

4gra opened this issue Apr 27, 2021 · 0 comments
Labels
reminder just a general reminder of a plan

Comments

@4gra
Copy link
Owner

4gra commented Apr 27, 2021

Chunked messages shouldn't require the user or the implementing command to have to negotiate multi-part messages, it should simply be detected and split as appropriate.

Messages which support / require chunk support should indicate this with $C or similar in the command json, so that the chunks can be auto-incremented (if a non-zero-terminated response is received?) and responses read - with the second chunk's prefix removed where appropriate.

This requires a new mode of interaction, a simple looped write / read / write which requires listening for a specific reply to a specific command, and therefore allowing read to give data back to the calling function rather than just spewing it to stdout.

@4gra 4gra added the reminder just a general reminder of a plan label Apr 27, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
reminder just a general reminder of a plan
Projects
None yet
Development

No branches or pull requests

1 participant