- Sort Score
- Result 10 results
- Languages All
Results 1 - 8 of 8 for Cancelling (0.06 sec)
-
okhttp-coroutines/README.md
but uses the standard Dispatcher in OkHttp. This means that by default Kotlin's Dispatchers are not used. Cancellation if implemented sensibly in both directions. Cancelling a coroutine scope, will cancel the call. Cancelling a call, will throw a CancellationException
Registered: Fri Sep 05 11:42:10 UTC 2025 - Last Modified: Thu Nov 09 15:47:27 UTC 2023 - 609 bytes - Viewed (0) -
okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/concurrent/Task.kt
* * Cancellation * ------------ * * Tasks may be canceled while they are waiting to be executed, or while they are executing. * * Canceling a task that is waiting to execute prevents that upcoming execution. Canceling a task * that is currently executing does not impact the ongoing run, but it does prevent a recurrence * from being scheduled. *
Registered: Fri Sep 05 11:42:10 UTC 2025 - Last Modified: Fri Dec 27 13:39:56 UTC 2024 - 2.4K bytes - Viewed (0) -
okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/connection/RoutePlanner.kt
* will prefer pooled connections. Only pooled HTTP/2 connections are used for such de-duplication. * * It is possible to cancel the finding process by canceling its call. * * Implementations of this interface are not thread-safe. Each instance is thread-confined to the * thread executing the call. */ interface RoutePlanner { val address: AddressRegistered: Fri Sep 05 11:42:10 UTC 2025 - Last Modified: Tue May 27 14:58:02 UTC 2025 - 4.2K bytes - Viewed (0) -
samples/guide/src/main/java/okhttp3/recipes/CancelCall.java
final long startNanos = System.nanoTime(); final Call call = client.newCall(request); // Schedule a job to cancel the call in 1 second. executor.schedule(() -> { System.out.printf("%.2f Canceling call.%n", (System.nanoTime() - startNanos) / 1e9f); call.cancel(); System.out.printf("%.2f Canceled call.%n", (System.nanoTime() - startNanos) / 1e9f); }, 1, TimeUnit.SECONDS);Registered: Fri Sep 05 11:42:10 UTC 2025 - Last Modified: Sat Jan 12 03:31:36 UTC 2019 - 2.1K bytes - Viewed (0) -
samples/guide/src/main/java/okhttp3/recipes/kt/CancelCall.kt
.build() val startNanos = System.nanoTime() val call = client.newCall(request) // Schedule a job to cancel the call in 1 second. executor.schedule({ System.out.printf("%.2f Canceling call.%n", (System.nanoTime() - startNanos) / 1e9f) call.cancel() System.out.printf("%.2f Canceled call.%n", (System.nanoTime() - startNanos) / 1e9f) }, 1, TimeUnit.SECONDS)
Registered: Fri Sep 05 11:42:10 UTC 2025 - Last Modified: Wed Mar 19 19:25:20 UTC 2025 - 2K bytes - Viewed (0) -
guava-testlib/src/com/google/common/util/concurrent/testing/TestingExecutors.java
* UnsupportedOperationException. * * <p>The implementation deviates from the {@code ExecutorService} specification with regards to * the {@code shutdownNow} method. First, "best-effort" with regards to canceling running tasks is * implemented as "no-effort". No interrupts or other attempts are made to stop threads executing * tasks. Second, the returned list will always be empty, as any submitted task is considered toRegistered: Fri Sep 05 12:43:10 UTC 2025 - Last Modified: Thu Jul 17 15:26:41 UTC 2025 - 6.6K bytes - Viewed (0) -
docs/distributed/DECOMMISSION.md
``` ### A pool not under decommissioning will throw an error ``` λ mc admin decommission status alias/ http://minio{1...2}/data{1...4} ERROR: This pool is not scheduled for decommissioning currently. ``` ## Canceling a decommission Stop an on-going decommission in progress, mainly used in situations when the load may be too high and you may want to schedule the decommission at a later point in time.Registered: Sun Sep 07 19:28:11 UTC 2025 - Last Modified: Mon Jul 11 14:59:49 UTC 2022 - 8.3K bytes - Viewed (0) -
android/guava-testlib/src/com/google/common/util/concurrent/testing/TestingExecutors.java
* UnsupportedOperationException. * * <p>The implementation deviates from the {@code ExecutorService} specification with regards to * the {@code shutdownNow} method. First, "best-effort" with regards to canceling running tasks is * implemented as "no-effort". No interrupts or other attempts are made to stop threads executing * tasks. Second, the returned list will always be empty, as any submitted task is considered toRegistered: Fri Sep 05 12:43:10 UTC 2025 - Last Modified: Thu Jul 17 15:26:41 UTC 2025 - 6.6K bytes - Viewed (0)