-
Notifications
You must be signed in to change notification settings - Fork 181
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
2 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cce51ca
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm curious about what this feature is for.
It's saying that if body is compressed always transfer as a single chunk?
cce51ca
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
exactly, my test byte vector was gzip compressed output.
cce51ca
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @jingpengw, yeah I noticed when you sent your report your data has a gz header.
I guess my question for @quinnj is why are we overriding the
chunksize
option for data where we've sniffed a compression header?The only place the
chunksize
option seems to be used is here inbody(io::IO, ...)
where we doread(r.body)
ifchunksize
is zsero orread(r.body, chunksize)
otherwise. However, it seems like the two types ofread
have the same behaviour because we've setchunksize = length(body) + 1
.i.e., wouldn't this have the same effect?