android/okhttp
1
0
Fork 0
mirror of https://github.com/square/okhttp.git synced 2026-01-24 04:02:07 +03:00
Code Releases Activity

Improve some Markdown

Browse Source
This commit is contained in:
Jesse Wilson
2014-01-25 11:44:14 -05:00
parent 93e079b936
commit 69cabb714e
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
concurrency.md
View File

@@ -34,7 +34,7 @@ The reader thread must never block on the application layer because this allows
It must never block on writing because this can deadlock the connection. Consider a client and server that both violate this rule. If you get unlucky, they could fill up their TCP buffers (so that writes block) and then use their reader threads to write a frame. Nobody is reading on either end, and the buffers are never drained.
### Do-stuff-later pool
#### Do-stuff-later pool
Sometimes there's an action required like calling the application layer or responding to a ping, and the thread discovering the action is not the thread that should do the work. We enqueue a runnable on this executor and it gets handled by one of the executor's threads.