-
Notifications
You must be signed in to change notification settings - Fork 48
Fix for running out of connections #29
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
base: master
Are you sure you want to change the base?
Conversation
|
Good catch. The only place it is needed though is in the GetResponsestring. I'll make the change e when I get to work |
|
I see, GetResponseStream closes the connection when the Stream closes. |
|
The other place I can think of is ViewResult. Perhaps this should implement IDisposable and close the HttpWebResponse there. Update: Oops. I see you're modifying the Extension class and not the CouchDatabase/ViewResult. If so, I'd recommend an optional argument (e.g. public static Document GetCouchDocument(this HttpWebResponse response, bool closeResponse=true)) so the extension methods don't carry the business logic of closing the connection. |
Conflicts: LoveSeat/Support/ResponseExtensionMethods.cs
Enable CouchDatabase to use different implementation of IObjectSerializer, typically in cases were custom configuration of JsonSerializerSettings is needed.
Conflicts: LoveSeat/Interfaces/IDocumentDatabase.cs LoveSeat/Interfaces/IViewResult.cs LoveSeat/ViewOptions.cs
refactored library to make more testable/injectable
This was because when the response was being read the response was not closed at the end. This meant that after 12xnumber cpu cores requests we were out of connections and just got timeouts.