Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better sharing for Executors (thread pools) #105

Closed
swankjesse opened this issue Feb 4, 2013 · 0 comments · Fixed by #118
Closed

Better sharing for Executors (thread pools) #105

swankjesse opened this issue Feb 4, 2013 · 0 comments · Fixed by #118

Comments

@swankjesse
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants