- Sort Score
- Result 10 results
- Languages All
Results 21 - 27 of 27 for transmitted (0.49 sec)
-
CHANGELOG.md
This should make it easier to use OkHttp in Gradle plugins. * Fix: Don't start the clock on response timeouts until the request body is fully transmitted. This is only relevant for duplex request bodies, because they are written concurrently when reading the response body.
Registered: Fri Sep 05 11:42:10 UTC 2025 - Last Modified: Mon Jul 07 19:32:33 UTC 2025 - 31.6K bytes - Viewed (1) -
docs/changelogs/changelog_3x.md
* **OkHttp now supports duplex calls over HTTP/2.** With normal HTTP calls the request must finish before the response starts. With duplex, request and response bodies are transmitted simultaneously. This can be used to implement interactive conversations within a single HTTP call. Create duplex calls by overriding the new `RequestBody.isDuplex()` method to return true.
Registered: Fri Sep 05 11:42:10 UTC 2025 - Last Modified: Sun Feb 06 14:55:54 UTC 2022 - 50.8K bytes - Viewed (0) -
okhttp/src/jvmTest/kotlin/okhttp3/internal/http2/HttpOverHttp2Test.kt
) val read = response1.body.source().read(ByteArray(8192)) assertThat(read).isEqualTo(8192) // Make a second call that should transmit the response headers. The response body won't be // transmitted until the flow-control window is updated from the first request. val call2 = client.newCall(Request(server.url("/"))) val response2 = call2.execute() assertThat(response2.code).isEqualTo(200)
Registered: Fri Sep 05 11:42:10 UTC 2025 - Last Modified: Fri Jun 20 11:46:46 UTC 2025 - 73.4K bytes - Viewed (0) -
okhttp/src/jvmTest/kotlin/okhttp3/URLConnectionTest.kt
fun flushAfterStreamTransmittedWithNoLengthHeaders() { testFlushAfterStreamTransmitted(TransferKind.END_OF_STREAM) } /** * We explicitly permit apps to close the upload stream even after it has been transmitted. We * also permit flush so that buffered streams can do a no-op flush when they are closed. * http://b/3038470 */ private fun testFlushAfterStreamTransmitted(transferKind: TransferKind) {
Registered: Fri Sep 05 11:42:10 UTC 2025 - Last Modified: Sat Jun 21 20:36:35 UTC 2025 - 133.2K bytes - Viewed (0) -
docs/es/docs/advanced/custom-response.md
{* ../../docs_src/custom_response/tutorial006c.py hl[2,7,9] *} ### `StreamingResponse` Toma un generador `async` o un generador/iterador normal y transmite el cuerpo del response. {* ../../docs_src/custom_response/tutorial007.py hl[2,14] *} #### Usando `StreamingResponse` con objetos similares a archivos
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Mon Dec 30 18:26:57 UTC 2024 - 12.5K bytes - Viewed (0) -
src/main/java/jcifs/pac/kerberos/KerberosEncData.java
Registered: Sun Sep 07 00:10:21 UTC 2025 - Last Modified: Sat Aug 16 01:32:48 UTC 2025 - 12.5K bytes - Viewed (0) -
docs/pt/docs/deployment/concepts.md
Isso ainda é verdade. Então, para poder ter **vários processos** ao mesmo tempo, tem que haver um **único processo escutando em uma porta** que então transmite a comunicação para cada processo de trabalho de alguma forma. ### Memória por Processo
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Sun May 11 13:37:26 UTC 2025 - 19.7K bytes - Viewed (0)