- Sort Score
- Result 10 results
- Languages All
Results 251 - 260 of 353 for sleeps (0.04 sec)
-
okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/connection/ConnectPlan.kt
import okhttp3.internal.platform.Platform import okhttp3.internal.tls.OkHostnameVerifier import okhttp3.internal.toHostHeader /** * A single attempt to connect to a remote server, including these steps: * * * [TCP handshake][connectSocket] * * Optional [CONNECT tunnels][connectTunnel]. When using an HTTP proxy to reach an HTTPS server
Registered: Fri Sep 05 11:42:10 UTC 2025 - Last Modified: Thu Jul 31 04:18:40 UTC 2025 - 18.6K bytes - Viewed (0) -
okhttp/src/commonJvmAndroid/kotlin/okhttp3/MultipartBody.kt
* both say in their comments that they're not really sure what the right approach is. We go * with Chrome's behavior (which also experimentally seems to match what IE does), but if you * actually want to have a good chance of things working, please avoid double-quotes, newlines, * percent signs, and the like in your field names. */
Registered: Fri Sep 05 11:42:10 UTC 2025 - Last Modified: Wed Mar 19 19:25:20 UTC 2025 - 10.9K bytes - Viewed (0) -
okhttp/src/jvmTest/kotlin/okhttp3/URLConnectionTest.kt
assertThat(server.takeRequest().exchangeIndex).isEqualTo(0) // Give the server time to enact the socket policy if it's one that could happen after the // client has received the response. Thread.sleep(500) val response2 = getResponse(newRequest("/b")) response1.body .source() .timeout() .timeout(100, TimeUnit.MILLISECONDS)
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/en/docs/async.md
For "synchronous" (contrary to "asynchronous") they commonly also use the term "sequential", because the computer / program follows all the steps in sequence before switching to a different task, even if those steps involve waiting. ### Concurrency and Burgers { #concurrency-and-burgers }
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Sun Aug 31 09:56:21 UTC 2025 - 24K bytes - Viewed (0) -
android/guava-tests/test/com/google/common/cache/CacheBuilderTest.java
} else if (behavior == 1) { // return null computeNullCount.incrementAndGet(); return null; } else if (behavior == 2) { // slight delay before returning Thread.sleep(5); computeCount.incrementAndGet(); return key; } else { computeCount.incrementAndGet(); return key; } } };
Registered: Fri Sep 05 12:43:10 UTC 2025 - Last Modified: Thu Aug 07 16:05:33 UTC 2025 - 25.1K bytes - Viewed (0) -
guava-tests/test/com/google/common/cache/CacheBuilderTest.java
} else if (behavior == 1) { // return null computeNullCount.incrementAndGet(); return null; } else if (behavior == 2) { // slight delay before returning Thread.sleep(5); computeCount.incrementAndGet(); return key; } else { computeCount.incrementAndGet(); return key; } } };
Registered: Fri Sep 05 12:43:10 UTC 2025 - Last Modified: Thu Aug 07 16:05:33 UTC 2025 - 25K bytes - Viewed (0) -
okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/cache2/Relay.kt
* * As bytes are returned from upstream they are written to a local file. Downstream sources read * from this file as necessary. * * This class also keeps a small buffer of bytes recently read from upstream. This is intended to * save a small amount of file I/O and data copying. */ class Relay private constructor( /**
Registered: Fri Sep 05 11:42:10 UTC 2025 - Last Modified: Wed May 28 17:15:47 UTC 2025 - 11.8K bytes - Viewed (0) -
android/guava-testlib/src/com/google/common/testing/GcFinalization.java
* } * * <p>Even if your non-test code does not use finalization, you can use this class to test for * leaks, by ensuring that objects are no longer strongly referenced: * * {@snippet : * // Helper function keeps victim stack-unreachable. * private WeakReference<Foo> fooWeakRef() { * Foo x = ....; * WeakReference<Foo> weakRef = new WeakReference<>(x); * // ... use x ...
Registered: Fri Sep 05 12:43:10 UTC 2025 - Last Modified: Mon Mar 17 20:26:29 UTC 2025 - 11.5K bytes - Viewed (0) -
docs/SMB3_IMPLEMENTATION_PLAN.md
3. **Reliability**: - Persistent handles survive 99% of network interruptions - Witness protocol achieves <5 second failover time 4. **Compatibility**: Works with Windows Server 2016+ and Azure Files ## Next Steps 1. **Immediate Actions**: - Set up Windows Server test environment - Create detailed technical specifications for Phase 1 - Identify and evaluate Java RDMA libraries 2. **Phase 1 Kickoff**:
Registered: Sun Sep 07 00:10:21 UTC 2025 - Last Modified: Sat Aug 16 02:53:50 UTC 2025 - 10.7K bytes - Viewed (0) -
docs/en/docs/release-notes.md
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Fri Sep 05 12:48:45 UTC 2025 - 544.1K bytes - Viewed (0)