Juraj Kirchheim

But of course this presumes that the underlying client can actually gradually read the data from the `Source`, which some platforms might not allow.

Progress is tricky, because in either direction content-length needn't be set. I guess this is roughly the best we can do: ```haxe interface HttpTransaction { var bytesWritten(get, never):Observable; var bytesRead(get,...

Hmm. Looking at the signature, I would probably expect to the progress to report on the download, rather than the upload. I'm still inclined to think that we might want...

Just to be clear: the above example is trivial of course. But in a complex method, if you forget to return in some branch, it goes unnoticed. That's the real...

Uhm, on its own it works quite fine, but I have some conceptual issues in tink_hxx's v1 to be resolved, because coconut.ui depends on both these breaking changes and those...

That's a "feature": #60 I'm not 100% sure that I like it, but the basic idea is that if the async computation is expensive, then it gets suspended if nobody...

Hmm, objection is a bit of a strong word. However it seems to me that regardless of ideal/real stream the container MUST close the connection if content-length was sent and...

Nah, your English is just fine! What I meant is that that I have a remark rather than an actual objection ;) So ok, assuming the container gets an error...

Hmm ... well ok, for one idealize should be fixed in *many* ways: 1. it should tell you how many bytes you've written, so that you can resume. 2. it...

Well, there are cases of course. Take an SQL result stream, that you map it through `function (o):Chunk return Json.strigify(o) + '\n'` and you have an ndjson stream where you...