A modern programming language that makes developers happier.

kotlinlang

I think that you shouldn't worry too much about API changes, as long as they're isolated to a single functionality. One of my ideas is to change request to have .upload and .download give back a wrapper (delegates to `Request`) that has extra functionality. That would also be a breaking API change.

That said:
I ám working on a generic stream in stream out approach that might work well in conjunction with number 3 and 2. It does nót get rid of .data, but by default give you the stream, as you propose, and only if you use .data it gets loaded into memory.

Number 1 and 4 are a no for me. 1 breaks expectations, 4 is meh because we all agree this is an issue.