- Sort Score
- Result 10 results
- Languages All
Results 1 - 5 of 5 for Microseconds (0.06 sec)
-
docs/en/docs/advanced/security/http-basic-auth.md
#### The time to answer helps the attackers { #the-time-to-answer-helps-the-attackers }Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Sun Aug 31 09:15:41 UTC 2025 - 5K bytes - Viewed (0) -
okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/concurrent/TaskRunner.kt
) : Lockable { private var nextQueueName = 10000 private var coordinatorWaiting = false private var coordinatorWakeUpAt = 0L /** * When we need a new thread to run tasks, we call [Backend.execute]. A few microseconds later we * expect a newly-started thread to call [Runnable.run]. We shouldn't request new threads until * the already-requested ones are in service, otherwise we might create more threads than we need. *Registered: Fri Sep 05 11:42:10 UTC 2025 - Last Modified: Sat Aug 30 11:30:11 UTC 2025 - 10.4K bytes - Viewed (0) -
docs/en/docs/async.md
Instead of that, by being an "asynchronous" system, once finished, the task can wait in line a little bit (some microseconds) for the computer / program to finish whatever it went to do, and then come back to take the results and continue working with them.
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Sun Aug 31 09:56:21 UTC 2025 - 24K bytes - Viewed (0) -
docs/en/docs/tutorial/bigger-applications.md
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Sun Aug 31 09:15:41 UTC 2025 - 19.1K bytes - Viewed (0) -
docs/fr/docs/async.md
À la place, en étant "asynchrone", une fois terminée, une tâche peut légèrement attendre (quelques microsecondes) que l'ordinateur / le programme finisse ce qu'il était en train de faire, et revienne récupérer le résultat.
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Sun Aug 31 09:56:21 UTC 2025 - 25.4K bytes - Viewed (0)