Open
Description
Repeatedly calling flush doesn't seem very optimal.
HTTPClient.executecallswriteAndFlushand because the body write isn't queued until the head has been written, the flush occurs immediately after the head has been written.TaskHandler.writeBodycallswriteAndFlush.
Ideally a simple HTTP request with one ByteBuffer shouldn't need to call flush until after the end part.
Metadata
Metadata
Assignees
Type
Projects
Milestone
Relationships
Participants
Activity
[-]AsyncHTTPClient calls flush after writing every part of the HTTP message[/-][+]AsyncHTTPClient calls flush after writing each part of the HTTP message[/+]