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

AsyncHTTPClient calls flush after writing each part of the HTTP message #203

Open
adam-fowler opened this issue Apr 22, 2020 · 0 comments · May be fixed by #214
Open

AsyncHTTPClient calls flush after writing each part of the HTTP message #203

adam-fowler opened this issue Apr 22, 2020 · 0 comments · May be fixed by #214
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@adam-fowler
Copy link
Member

Repeatedly calling flush doesn't seem very optimal.

  • HTTPClient.execute calls writeAndFlush and because the body write isn't queued until the head has been written, the flush occurs immediately after the head has been written.
  • TaskHandler.writeBody calls writeAndFlush.

Ideally a simple HTTP request with one ByteBuffer shouldn't need to call flush until after the end part.

@adam-fowler adam-fowler changed the title AsyncHTTPClient calls flush after writing every part of the HTTP message AsyncHTTPClient calls flush after writing each part of the HTTP message Apr 22, 2020
@artemredkin artemredkin self-assigned this May 7, 2020
@artemredkin artemredkin added the enhancement New feature or request label May 13, 2020
@artemredkin artemredkin added this to the 1.2.0 milestone May 13, 2020
@artemredkin artemredkin linked a pull request May 18, 2020 that will close this issue
@artemredkin artemredkin modified the milestones: 1.2.0, 1.2.1 Jul 30, 2020
@artemredkin artemredkin modified the milestones: 1.2.1, 1.2.2 Aug 20, 2020
@artemredkin artemredkin modified the milestones: 1.2.2, 1.2.3 Nov 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants