Skip to content

Conversation

@technige
Copy link
Contributor

No description provided.

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.

4 participants