Skip to content

1.0 session pool #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

Merged
merged 8 commits into from
Jan 15, 2016
Merged

1.0 session pool #29

merged 8 commits into from
Jan 15, 2016

Conversation

technige
Copy link
Contributor

No description provided.

@@ -341,6 +355,11 @@ def __enter__(self):
def __exit__(self, exc_type, exc_value, traceback):
self.close()

def reset(self):
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should reset really be a user-facing feature? I'd argue we should encourage users of the Session API to simply close sessions if they are unclear about their state, unless there's a good use case that warrants doing this instead?

@jakewins
Copy link
Contributor

This is brilliant, super happy to see this come together. I'd love a test that ensures the defunct functionality works - perhaps one that checks that we can handle a fatal error occurring on the connection by stubbing out the underlying channel or something, and one that checks that the pool recovers if the server dies?

pontusmelke added a commit that referenced this pull request Jan 15, 2016
@pontusmelke pontusmelke merged commit e57aef2 into 1.0 Jan 15, 2016
@zhenlineo zhenlineo deleted the 1.0-session-pool branch May 23, 2016 15:31
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