- Sort Score
- Result 10 results
- Languages All
Results 1 - 2 of 2 for Idle (0.02 sec)
-
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. * public final OkHttpClient client = new OkHttpClient(); * ``` *
Registered: Fri Nov 01 11:42:11 UTC 2024 - Last Modified: Sat Apr 06 04:21:33 UTC 2024 - 52K bytes - Viewed (0) -
docs/changelogs/changelog_3x.md
be called. Web sockets have always been had pings, but pings on HTTP/2 connections is new in this release. Pings are used for connections that are busy carrying calls and for idle connections in the connection pool. (Pings do not impact when pooled connections are evicted). If you have a configured ping interval, you should confirm that it is long
Registered: Fri Nov 01 11:42:11 UTC 2024 - Last Modified: Sun Feb 06 14:55:54 UTC 2022 - 50.8K bytes - Viewed (0)