-
Notifications
You must be signed in to change notification settings - Fork 325
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
Non persistent connections #296
base: master
Are you sure you want to change the base?
Conversation
@@ -110,6 +110,7 @@ class TestConfig: | |||
interactive = False | |||
verbose = False | |||
ssl_insecure = False | |||
non_persistent = False # Disables keep-alive pycurl option |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would be nice to specify testing -vs- benchmarking here. Not sure how hard that would be though.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While this absolutely fixes an issue I'm seeing with django2 (http/1.1), should the fix be hidden behind a command line flag, or, does pycurl's reuse make the old reuse simply redundant?
Actually, the latest version of pycurl already takes care of handle reuse on its own by resetting instead of closing, the explicit handle reuse in the framework is no longer necessary and, in my personal opinion, confusing - simple is better than complex, right? -, now, in regards to tcp persistent connections I rather this to be optional to avoid issues in very complicated use cases - don't want to ruin it for anyone else. |
Added an option to disable persistent connections in order to avoid issues with Django