- Sort Score
- Result 10 results
- Languages All
Results 11 - 20 of 128 for track (0.16 sec)
-
okhttp/src/main/kotlin/okhttp3/internal/cache/DiskLruCache.kt
* * o DIRTY lines track that an entry is actively being created or updated. Every successful * DIRTY action should be followed by a CLEAN or REMOVE action. DIRTY lines without a matching * CLEAN or REMOVE indicate that temporary files may need to be deleted. * * o CLEAN lines track a cache entry that has been successfully published and may be read. A
Plain Text - Registered: Fri May 03 11:42:14 GMT 2024 - Last Modified: Mon Jan 08 01:13:22 GMT 2024 - 34.7K bytes - Viewed (0) -
architecture/networking/controllers.md
Running the controller actually starts processing things. Normally, this just means running the queue. All informers created by `kube.Client` are kept track in the client, and started in one go with `RunAndWait` in one centralized call. As a result, each individual controllers should simply wait until informers have synced, then run the queue to start processing things.
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Fri Feb 09 17:41:25 GMT 2024 - 4.9K bytes - Viewed (0) -
okhttp/src/main/kotlin/okhttp3/internal/concurrent/TaskRunner.kt
val name = lock.withLock { nextQueueName++ } return TaskQueue(this, "Q$name") } /** * Returns a snapshot of queues that currently have tasks scheduled. The task runner does not * necessarily track queues that have no tasks scheduled. */ fun activeQueues(): List<TaskQueue> { lock.withLock { return busyQueues + readyQueues } } fun cancelAll() { lock.assertHeld()
Plain Text - Registered: Fri May 03 11:42:14 GMT 2024 - Last Modified: Mon Apr 29 00:33:04 GMT 2024 - 10.6K bytes - Viewed (0) -
README.md
We highly recommend you keep OkHttp up-to-date. As with auto-updating web browsers, staying current with HTTPS clients is an important defense against potential security problems. [We track][tls_history] the dynamic TLS ecosystem and adjust OkHttp to improve connectivity and security. OkHttp uses your platform's built-in TLS implementation. On Java platforms OkHttp also supports
Plain Text - Registered: Fri May 03 11:42:14 GMT 2024 - Last Modified: Wed Dec 20 23:27:07 GMT 2023 - 6.2K bytes - Viewed (0) -
docs/changelogs/changelog_4x.md
automatically retry on an unshared connection. * Fix: Don't crash if a TLS tunnel's response body is truncated. * Fix: Don't track unusable routes beyond their usefulness. We had a bug where we could track certain bad routes indefinitely; now we only track the ones that could be necessary. * Fix: Defer proxy selection until a proxy is required. This saves calls to `ProxySelector` on
Plain Text - Registered: Fri May 03 11:42:14 GMT 2024 - Last Modified: Wed Apr 17 13:25:31 GMT 2024 - 25.2K bytes - Viewed (0) -
common-protos/k8s.io/api/admission/v1/generated.proto
// otherwise identical (parallel requests, requests when earlier requests did not modify etc) // The UID is meant to track the round trip (request/response) between the KAS and the WebHook, not the user request. // It is suitable for correlating log entries between the webhook and apiserver, for either auditing or debugging. optional string uid = 1;
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Mon Mar 11 18:43:24 GMT 2024 - 8.1K bytes - Viewed (0) -
docs/features/events.md
### EventListener.Factory
Plain Text - Registered: Fri May 03 11:42:14 GMT 2024 - Last Modified: Sun Feb 06 02:19:09 GMT 2022 - 7.7K bytes - Viewed (0) -
docs/features/interceptors.md
Interceptors can be chained. Suppose you have both a compressing interceptor and a checksumming interceptor: you'll need to decide whether data is compressed and then checksummed, or checksummed and then compressed. OkHttp uses lists to track interceptors, and interceptors are called in order. ![Interceptors Diagram](../assets/images/******@****.***) ### Application Interceptors
Plain Text - Registered: Fri May 03 11:42:14 GMT 2024 - Last Modified: Sun Feb 06 02:19:09 GMT 2022 - 8.1K bytes - Viewed (0) -
common-protos/k8s.io/api/admission/v1beta1/generated.proto
// otherwise identical (parallel requests, requests when earlier requests did not modify etc) // The UID is meant to track the round trip (request/response) between the KAS and the WebHook, not the user request. // It is suitable for correlating log entries between the webhook and apiserver, for either auditing or debugging. optional string uid = 1;
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Mon Mar 11 18:43:24 GMT 2024 - 8.1K bytes - Viewed (0) -
docs/features/https.md
Plain Text - Registered: Fri May 03 11:42:14 GMT 2024 - Last Modified: Sat Dec 24 00:16:30 GMT 2022 - 10.5K bytes - Viewed (0)