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
The current behavior when writing a chunked body with into_buffered() is currently not as intended as the buffer seems to be on the wrong side of the chunked writer.
Currently many small chunks are encoded and written to the buffer. Instead of the small body writes should somehow be buffered before the ChunkedBodyWriter such that the buffered content is written in a large chunk.
What I am seeing right now is a request body with waaay to many chunks of only a few bytes which corresponds to each write to the body. Instead I want the small writes to be buffered and only when the buffer is full/flushed should the chunk be written.
This commit:
* Moves the responsibility for writing the request body from `Request` to `HttpConnection`.
* Uses the buffer provided when calling `into_buffered()` to buffer writes before they are passed on to the `ChunkedBufferWriter`
This fixesdrogue-iot#71
This commit:
* Moves the responsibility for writing the request body from `Request` to `HttpConnection`.
* Uses the buffer provided when calling `into_buffered()` to buffer writes before they are passed on to the `ChunkedBufferWriter`
This fixesdrogue-iot#71
The current behavior when writing a chunked body with
into_buffered()
is currently not as intended as the buffer seems to be on the wrong side of the chunked writer.Currently many small chunks are encoded and written to the buffer. Instead of the small body writes should somehow be buffered before the
ChunkedBodyWriter
such that the buffered content is written in a large chunk.What I am seeing right now is a request body with waaay to many chunks of only a few bytes which corresponds to each write to the body. Instead I want the small writes to be buffered and only when the buffer is full/flushed should the chunk be written.
cc @bugadani
The text was updated successfully, but these errors were encountered: