-
Notifications
You must be signed in to change notification settings - Fork 945
Open
Description
Over the past two or three weeks, I’ve tried to write some simple test code using tokio-quiche, but I ran into many issues. For example:
- If
process_readsdoes not read data in time (e.g. to apply backpressure), it will not be called again. - If
wait_for_dataor other callbacks are not implemented correctly (what is a “correct” implementation?), the CPU may spin at 100%.
My question is: why doesn’t tokio-quiche provide a more ergonomic API? For example:
ConnandStreamobjectsopen_streamandaccept_streammethods
I have read the article
https://blog.cloudflare.com/async-quic-and-http-3-made-easy-tokio-quiche-is-now-open-source/
but I still don’t see a convincing reason for this design choice.
I would appreciate some clarification. Thank you.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels