network/io.github.maniramezan.kenwork.network/NetworkClient

NetworkClient

class NetworkClient(configuration: NetworkClientConfiguration = NetworkClientConfiguration()) : NetworkDataSource

Coroutine-based HTTP client built on Ktor + OkHttp. The Kotlin counterpart of SwiftyNetwork's NetworkClient.

Responsibilities, per request:

Resolve authorization (endpoint-level, else the configured AuthorizationProvider).
Execute the call.
On 401, refresh the credential and retry up to NetworkClientConfiguration.maxAuthRefreshAttempts.
Map non-2xx and transport failures to NetworkError.
Decode the success body into the requested type.

Thread-safe: the mutable configuration/client pair is guarded by a Mutex, and the active client is reference-counted so updateConfiguration never closes a client mid-request.

Constructors

NetworkClient

constructor(configuration: NetworkClientConfiguration = NetworkClientConfiguration())

Types

Companion

object Companion

Functions

suspend fun close()

Closes the underlying HTTP client after in-flight requests complete. Once closed, this client cannot make requests or accept configuration updates.

execute

suspend fun ApiClient.execute(endpoint: NetworkEndpoint)

Executes endpoint, discarding any response body.

request

open suspend override fun <T> request(endpoint: NetworkEndpoint, body: Any?, bodyType: TypeInfo?, responseType: TypeInfo): T

Executes endpoint, optionally sending body (described by bodyType), and decodes the response into responseType.

request

inline suspend fun <T> ApiClient.request(endpoint: NetworkEndpoint): T

Executes endpoint and decodes the response into T.

inline suspend fun <B, T> ApiClient.request(endpoint: NetworkEndpoint, body: B): T

Executes endpoint sending body of type B, and decodes the response into T.

updateConfiguration

suspend fun updateConfiguration(newConfiguration: NetworkClientConfiguration)

Swaps in a new NetworkClientConfiguration, rebuilding the underlying engine. The previous client is closed only once its in-flight requests complete, so reconfiguring mid-request is safe.