Closed ostrolucky closed 5 years ago
There's no technical reason against introducing a setter for it.
However I am curious what is your use case?
This is so program can tweak the chunk size being used based on current r/w speeds
I strongly doubt it will bring any benefit, but I'm open to seeing actual benchmarks and be told otherwise (i.e. add your own setter for testing and bench it then).
In that case having it in constructor would also be questionable, wouldn't it?
I'm fine with a setter there, do you want to provide a PR?
I would like to change the
chunksize
duringResouce(Input|Output)Stream
object lifecycle, not just when constructing it. Can we have chunksize mutator, or optional argument inread
?