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

Correctly dispose objects to release HTTP connections #15

Merged
merged 1 commit into from
Aug 28, 2015

Conversation

JSkimming
Copy link
Owner

During live usage I discovered the maximum HTTP connections (defaults to 2) were excused, as a result the application hung on the third request. The fix is to correctly dispose of the HTTP request/response objects, something I thought unnecessary for HttpClient.

👍 to @robcthegeek, who resolutely disposed of the request/response objects when we worked together on another project 😄

During live usage I discovered the maximum HTTP connections (defaults to
2) were excused, as a result the application hung on the third request.
The fix is to correctly dispose of the HTTP request/response objects,
something I thought unnecessary for HttpClient.
JSkimming added a commit that referenced this pull request Aug 28, 2015
Correctly dispose objects to release HTTP connections
@JSkimming JSkimming merged commit fa94f83 into master Aug 28, 2015
@JSkimming JSkimming deleted the release-connections branch August 28, 2015 13:29
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 this pull request may close these issues.

1 participant