You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently each SPDY connection creates its own ExecutorService for read, write and callbacks. We could do the same work with fewer resources by using fewer ExecutorServices.
Along with this we should improve thread naming, so that stack dumps show application-level thread information, like SPDY reader: http://api.squareup.com or SPDY callback: http://api.squareup.com stream 5.
The text was updated successfully, but these errors were encountered:
Currently each SPDY connection creates its own ExecutorService for read, write and callbacks. We could do the same work with fewer resources by using fewer ExecutorServices.
Along with this we should improve thread naming, so that stack dumps show application-level thread information, like
SPDY reader: http://api.squareup.com
orSPDY callback: http://api.squareup.com stream 5
.The text was updated successfully, but these errors were encountered: