- Sort Score
- Result 10 results
- Languages All
Results 1 - 4 of 4 for structure (0.15 sec)
-
okhttp/src/main/kotlin/okhttp3/ResponseBody.kt
* * There is no benefit to invoking multiple `close()` methods for the same response body. * * For synchronous calls, the easiest way to make sure a response body is closed is with a `try` * block. With this structure the compiler inserts an implicit `finally` clause that calls * [close()][Response.close] for you. * * ```java * Call call = client.newCall(request); * try (Response response = call.execute()) {
Plain Text - Registered: Fri May 03 11:42:14 GMT 2024 - Last Modified: Mon Jan 08 01:13:22 GMT 2024 - 10.7K bytes - Viewed (0) -
okhttp/src/main/kotlin/okhttp3/EventListener.kt
* each event pair are used to link the event in case of concurrent or repeated events e.g. * `dnsStart(call, domainName)` → `dnsEnd(call, domainName, inetAddressList)`. * * Events are typically nested with this structure: * * * call ([callStart], [callEnd], [callFailed]) * * proxy selection ([proxySelectStart], [proxySelectEnd]) * * dns ([dnsStart], [dnsEnd]) * * connect ([connectStart], [connectEnd], [connectFailed])
Plain Text - Registered: Fri May 03 11:42:14 GMT 2024 - Last Modified: Mon Jan 08 01:13:22 GMT 2024 - 15.2K bytes - Viewed (0) -
okhttp/src/main/kotlin/okhttp3/Cache.kt
import okio.buffer /** * Caches HTTP and HTTPS responses to the filesystem so they may be reused, saving time and * bandwidth. * * The Cache instance must have exclusive access to the [directory], since the internal data structures * may cause corruption or runtime errors if not. It may however be shared amongst multiple OkHttpClient * instances. * * ## Cache Optimization *
Plain Text - Registered: Fri May 03 11:42:14 GMT 2024 - Last Modified: Wed Apr 10 19:46:48 GMT 2024 - 26.8K bytes - Viewed (0) -
okhttp/src/test/java/okhttp3/internal/connection/FastFallbackExchangeFinderTest.kt
import org.junit.jupiter.api.Test /** * Unit test for [FastFallbackExchangeFinder] implementation details. * * This test uses [TaskFaker] to deterministically test racy code. Each function in this test has * the same structure: * * * prepare a set of plans, each with a predictable connect delay * * attempt to find a connection * * step through time, asserting that the expected side effects are performed. */
Plain Text - Registered: Fri May 03 11:42:14 GMT 2024 - Last Modified: Wed Apr 24 04:40:49 GMT 2024 - 20.9K bytes - Viewed (0)