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

Non persistent connections #296

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

eespitiarea
Copy link

Added an option to disable persistent connections in order to avoid issues with Django

@@ -110,6 +110,7 @@ class TestConfig:
interactive = False
verbose = False
ssl_insecure = False
non_persistent = False # Disables keep-alive pycurl option
Copy link

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.

Copy link

@CodeMonk CodeMonk left a 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?

@eespitiarea
Copy link
Author

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.

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.

3 participants