-
Notifications
You must be signed in to change notification settings - Fork 25
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
RTN12c #163
RTN12c #163
Conversation
@@ -414,6 +414,13 @@ class TestProxyTransport: ARTWebSocketTransport { | |||
super.receive(msg) | |||
} | |||
|
|||
func closeAbruptly() { | |||
// Inject a ProtocolMessage.CLOSE |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think this is a valid mock, because if the real transport does indeed close abruptly it won't make up a ProtocolMessage.CLOSE. I guess the connection should be notified of the close somehow (with a callback, I guess) and then check the current state, so that if it is CLOSING it transitions to CLOSED.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agreed, this is completely the wrong behaviour. We want the transport on(closed)
event equivalent to be triggered by the test suite so that the client library thinks the transport was abruptly terminated.
b755c20
to
7a417f0
Compare
Rebased with changes. |
https://github.com/ably/ably-ios/blob/b755c200717e81188651c8bdb19bf71f31b9d7d6/ably-ios/ARTWebSocketTransport.m#L251 I think the |
LGTM |
1 similar comment
LGTM |
It's important to merge #169 first, remove 435317c, rebase with master and check if it's ok. |
7a417f0
to
613194d
Compare
Passing