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
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.
The text was updated successfully, but these errors were encountered:
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
Repeatedly calling
flush
doesn't seem very optimal.HTTPClient.execute
callswriteAndFlush
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
callswriteAndFlush
.Ideally a simple HTTP request with one
ByteBuffer
shouldn't need to call flush until after the end part.The text was updated successfully, but these errors were encountered: