Skip to content

Introduce ConnectionPoolKeyStrategy #214

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

Merged
merged 1 commit into from
Feb 9, 2013
Merged

Introduce ConnectionPoolKeyStrategy #214

merged 1 commit into from
Feb 9, 2013

Conversation

slandelle
Copy link
Contributor

The general idea is to be able to control at request level the connection used to sent it.
This is implemented with an optional ConnectionPoolKeyStrategy passed on the Request object.

For example, one can pass a ConnectionPoolKeyStrategy that combines a user UUID the default DefaultConnectionPoolStrategy.

Currently only works for Netty provider.

Only works for NettyProvider
jfarcand added a commit that referenced this pull request Feb 9, 2013
Introduce ConnectionPoolKeyStrategy
@jfarcand jfarcand merged commit 05ae8da into AsyncHttpClient:master Feb 9, 2013
@slandelle
Copy link
Contributor Author

Thanks!

Do you want me to port it back to 1.7.x?

@jfarcand
Copy link
Contributor

Good idea!

@slandelle
Copy link
Contributor Author

Will do today

@slandelle
Copy link
Contributor Author

Done

jfarcand pushed a commit that referenced this pull request Feb 11, 2013
jfarcand added a commit that referenced this pull request Feb 11, 2013
rlubke added a commit that referenced this pull request Feb 22, 2013
rlubke added a commit that referenced this pull request Feb 22, 2013
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.

2 participants