- Sort Score
- Result 10 results
- Languages All
Results 1 - 2 of 2 for polos (0.14 sec)
-
docs/changelogs/changelog_3x.md
In OkHttp 3.x, each new `OkHttpClient` gets its own private connection pool. Applications should avoid creating many connection pools as doing so prevents connection reuse. Each connection pool holds its own set of connections alive so applications that have many pools also risk exhausting memory! The best practice in OkHttp 3 is to create a single OkHttpClient instance
Plain Text - Registered: Fri May 03 11:42:14 GMT 2024 - Last Modified: Sun Feb 06 14:55:54 GMT 2022 - 50.8K bytes - Viewed (0) -
okhttp/src/main/kotlin/okhttp3/OkHttpClient.kt
* your HTTP calls. This is because each client holds its own connection pool and thread pools. * Reusing connections and threads reduces latency and saves memory. Conversely, creating a client * for each request wastes resources on idle pools. * * Use `new OkHttpClient()` to create a shared instance with the default settings: * * ```java * // The singleton HTTP client.
Plain Text - Registered: Fri May 03 11:42:14 GMT 2024 - Last Modified: Sat Apr 06 04:21:33 GMT 2024 - 52K bytes - Viewed (0)