Kevin Leung
Kevin Leung
Hm... should even split to uploadProgress and downloadProgress
and need a way to abort
Can we still include content length and make it `Optional`?
Now we have `tink.state.Progress`, any new API proposal here?
I think it is just: ```haxe function request(req:OutgoingRequest):Progress; ```
I wrongly thought that the response is only available after the upload is finished but it should not be the case. I think HTTP can produce a response header as...
Related: https://github.com/haxetink/tink_http/commit/13413e2f16cfe53fc8cd987928310729ee33156d I added that because nodejs will crash when the status code is outside such range.
There is no such API currently. You can instead use `Future#first` to manually create a timeout ```haxe Future.delay(300, Failure(new Error('Timed out'))).first(Client.fetch(...)); ```
Or introducing another meta besides `await` and `async` which is used to only indicate there are something to get transformed inside?
Oh I thought `@:await` forces the function to return `Void`. If that's not the case, this can be closed.