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.

Sign up for GitHub

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

Jump to bottom

multipart parser may use chronos's readMessage api avoiding store buffer in parser #38

Open
bung87 opened this issue Aug 20, 2021 · 0 comments
Open

multipart parser may use chronos's readMessage api avoiding store buffer in parser #38

bung87 opened this issue Aug 20, 2021 · 0 comments
Labels
enhancement New feature or request

Comments

@bung87
Copy link
Owner

bung87 commented Aug 20, 2021 •
edited

chronos already buffered.

may use chronos's readMessage api

proc readMessage*(transp: StreamTransport,
                  predicate: ReadMessagePredicate) {.async.} =

https://github.com/status-im/nim-chronos/blob/9d80c7068f6d6404dbd4d25eee11fda3af796bfa/chronos/transports/stream.nim#L2384
@bung87 bung87 added the enhancement New feature or request label Aug 20, 2021
@bung87 bung87 changed the title multipart parser read byte one by one may use chronos's readMessage api multipart parser may use chronos's readMessage api avoiding store buffer in parser Sep 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@bung87