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

RTN16d #394

Merged
merged 1 commit into from
Apr 27, 2016
Merged

RTN16d #394

merged 1 commit into from
Apr 27, 2016

Conversation

ricardopereira
Copy link
Contributor

No description provided.

@tcard
Copy link
Contributor

tcard commented Apr 27, 2016

LGTM

@tcard tcard merged commit 0f8daa9 into master Apr 27, 2016
@tcard tcard deleted the rtn16d branch April 27, 2016 15:13
let firstConnectionDetails = transport.protocolMessagesReceived.filter{ $0.action == .Connected }.first!.connectionDetails
expect(firstConnectionDetails!.connectionKey).toNot(beNil())
expect(clientRecover.connection.id).to(equal(expectedConnectionId))
expect(clientRecover.connection.key).to(equal(firstConnectionDetails!.connectionKey))
Copy link
Member

Choose a reason for hiding this comment

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

I am not sure this is right, the connection key can change when the connection is recovered, the only guarantee is that the connection ID remains the same

Copy link
Contributor

Choose a reason for hiding this comment

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

This is right. It's checking that the connection key is the new one received in the CONNECTED message from the server (firstConnectionDetails), not that it's keeping the old connection key. (Maybe the name firstConnectionDetails is a bit misleading?)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes, it should be something like recoveredConnectionDetails :/

@mattheworiordan
Copy link
Member

Please review as I am not sure this is correct @tcard @ricardopereira

tcard pushed a commit that referenced this pull request May 16, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants