The library should probably use KTOR

[kaidotarma]

The library doesn't use KTOR - is this planned or not?
For the KMP consumers, KTOR is the standard networking library, and would be much better to handle the intercepting in the common code.
Right now, there is a need to set up request interception (for authentication, etc) per platform.

[marekpelc-pega]

It is a good point, but it would require significant effort to reimplement our engines using Ktor, so we will not be doing that in the near future.

[kaidotarma]

Hi!

Another easy option would be to make the SDK implementation more generic by changing:
https://github.com/pegasystems/constellation-mobile-sdk/blob/master/engine-webview/src/androidMain/kotlin/com/pega/constellation/sdk/kmp/engine/webview/android/AndroidWebViewEngine.kt
to take in Call.Factory instead of OkHttpClient.
A similar change would then be needed in WebViewNetworkInterceptor, to take in Call.Factory instead of OkHttpClient and also to handle Call.Factory.execute instead of OkHttpClient.execute.

Then the SDK users could create their own middle-man converting OkHttp requests into Ktor requests, and after request converting Ktor response into OkHttp response.

This would open up the possibility to use Ktor with your library by changing 3 lines of code in the SDK.
It would not break existing logic and OkHttpClient could still be passed as an argument as well.
Would you please consider this option?

[kaidotarma]

@marekpelc-pega @lukaszgajewski-pega I'm currently looking into how we can manage OkHttp3 and Ktor together. No need to do changes on the library until then. ;)