Can Ferrostar use Ktor-client-http instead of okhttp3?

[AIBappa]

I am trying to integrate Ferrostar in my Kotlin multiplatform app for navigation but getting build errors due to the dependency on Okhttp3 (JVM and not JS). Can we use a JS based library like Ktor instead?

[Archdoog]

I'm not opposed to this. I like ktor and am all for cross compatibility. Would you be able to whip up a small discussion/RFD here (per our contributor guide: https://stadiamaps.github.io/ferrostar/contributing.html#issues-vs-discussions)? It should briefly summarize how we can do this and any impacts to existing developers it may have? Some key questions I'd want to understand are:

1. Is it possible to abstract things such that a developer can use their dependency of choice for kotlin http? If so, is it worth the effort versus just moving this project to Ktor and dropping Okhttp.
2. Are there other things we should consider when trying to enable support for Android and KMP? I just don't have experience here at this time to understand implications.
3. Is it ok to use Ktor with other http dependencies? E.g. if an app already uses okhttp for another purpose.
4. Any other useful notes that come to mind.

This RFD discussion should let us create some issues that you and/or other contributors can use to accomplish the agreed goal.

[ben-burwood]

See here, which can be implemented with v0.36 for Ktor Http client Implementation
https://gist.github.com/ben-burwood/a42c8efb45e406b37d6eddc6cd42e63f