You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 28, 2023. It is now read-only.
the generated server is agressive in flushing the write stream, e.g. here.
This may result in tcp packets being sent with just header information, since flush is called, and result in double the http framing overhead.
Do we need the immediate flush of headers in the case that a result can be provided on the channel in a synchronous fashion? is there a way to only flush headers after a few milliseconds if an immediate result is not forthcoming from the handler?
The text was updated successfully, but these errors were encountered:
Thank you for submitting your first issue to this repository! A maintainer will be here shortly to triage and review.
In the meantime, please double-check that you have provided all the necessary information to make this process easy! Any information that can help save additional round trips is useful! We currently aim to give initial feedback within two business days. If this does not happen, feel free to leave a comment.
Please keep an eye on how this issue will be labeled, as labels give an overview of priorities, assignments and additional actions requested by the maintainers:
"Priority" labels will show how urgent this is for the team.
"Status" labels will show if this is ready to be worked on, blocked, or in progress.
"Need" labels will indicate if additional input or analysis is required.
the generated server is agressive in flushing the write stream, e.g. here.
This may result in tcp packets being sent with just header information, since flush is called, and result in double the http framing overhead.
Do we need the immediate flush of headers in the case that a result can be provided on the channel in a synchronous fashion? is there a way to only flush headers after a few milliseconds if an immediate result is not forthcoming from the handler?
The text was updated successfully, but these errors were encountered: