yeah, I pretty much agree with you. I originally designed it to be able to solve common problems. But, I think it is either the design, or the default implementation wasn’t good enough.

Do you mind open a PR to fix it?

Perhaps, generalize it to accommodate other use cases as well

I am not sure yet, how to better handle this situation in general.. but I am still thinking of it

meanwhile, there's another problem I have come across: you can't add or remove parameters from a

Request

because they are stored in a

val parameters: List<...> = listOf()

I cannot understand why is this, because everything else in the

Request

is mutable

and I am not sure how we are supposed to add or remove parameters from a

Request

if we need it

What would be the best way to limit the amount of async requests that are fired at the same time? Say I have a loop that does requests on a set of 70000 ids to an api. Rightfully, the api pretty quickly shuts my requests down with “429: Too many requests”. I would like to have some way of only doing a few at a time and wait for some of the requests to return before firing the next.

Use the synchronized version maybe?

Figured I'd rather type it out on SO: https://stackoverflow.com/questions/48585651/using-fuels-responseobject-with-a-generic-call-site

I'm kinda stuck centralizing my calls with Fuel, but I've this nagging feeling that I'm simply missing another way to do this.

if that is the case, have you checked this all? https://github.com/kittinunf/Fuel/blob/master/fuel/src/test/kotlin/com/github/kittinunf/fuel/RequestPathStringConvertibleExtensionTest.kt

any plans to support sessions? e.g. creating stateful connection that passes in cookies and maybe shares tcp connection for subsequent requests?

how does fuel achieve asynchronous responses?

I did a thing! Is this the sort of thing that I should consider contributing back? (Any interest in a PR?)

would be nice if it used coroutines

I think it looks good but it probably might be published as extension?

Yeah, I can make it an extension. It's somewhat already built like that, as it doesn't directly modify Fuel itself.

@poohbar where do you think it should use coroutines? I suppose I don't see where you think it would need them

Converting

Fuel

to coroutines seems like a major redesign since fuel is callback based. https://github.com/jkcclemens/khttp seems like more suitable library for coroutines for now.

Hi

anybody only . i need a help

i have been trying post multipart file upload but request only picks file and it omits formdata

@hyper.gazer uploaded a file: request

this is how my request look like. i tried without file (passing empty dataparts) and request picks up formdata . but when i try to use it with datapart it wont sent parameters

hi guys I am hoping to make some contributions to fuel in the next few months

hi I have a pr open for an issue I have raised I would love to hear any feed back

I have had a further idea for the coroutines Extensions, I was going to add more methods that return Result<T> rather than T and throwing an exception