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

why sending data after headers and body fully get ready #7

Open
togear opened this issue Aug 11, 2023 · 0 comments
Open

why sending data after headers and body fully get ready #7

togear opened this issue Aug 11, 2023 · 0 comments

Comments

@togear
Copy link

togear commented Aug 11, 2023

I'm wondering why in this module QUIC's transmission method is not streaming, but rather waits to download the headers and body fully before sending to the client. Intuitively, it seems this could be detrimental for fast response times, as it likely increases the first packet delay. What were the considerations for having QUIC wait for all data before sending, rather than streaming chunks incrementally?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant