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

hackney 2.0 roadmap #275

Closed
benoitc opened this Issue Jan 25, 2016 · 5 comments

Comments

Projects
None yet
3 participants
@benoitc
Owner

benoitc commented Jan 25, 2016

Tasks for the hackney 2.0 version

  • new manager to reuse connections #276
  • full ipv6 support, eyeball strategy #206
  • relax URL encoding #277
  • improve proxy support
  • improve HTTP 1.1 support
@edgurgel

This comment has been minimized.

Collaborator

edgurgel commented Jan 25, 2016

👍

@lazedo

This comment has been minimized.

lazedo commented Feb 5, 2016

@benoitc Hi, maybe this would be a good time to introduce min_pool_size or min_available. sometimes there are a lot of simultaneous requests and i think we could benefit in performance if we had min_pool_size connections ready. thoughts ?

@benoitc

This comment has been minimized.

Owner

benoitc commented Feb 6, 2016

@lazedo how would it works? preconnecting resources? or something else?

@lazedo

This comment has been minimized.

lazedo commented Feb 6, 2016

@benoitc yes, preconnecting resources and keep them alive

@benoitc

This comment has been minimized.

Owner

benoitc commented Feb 9, 2016

@lazedo well there will be pre-connection, but keeping a minimum alive may create a network congestion. Servers don't like to have too much connections to them from the same origin. I add it to the todo list.

@benoitc benoitc closed this Aug 26, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment