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.
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[/+]on Apr 22, 2020
Activity
[-]AsyncHTTPClient calls flush after writing every part of the HTTP message[/-][+]AsyncHTTPClient calls flush after writing each part of the HTTP message[/+]