HRC - double killConnection opens a new socket without disconnection
Posted: 09 Jan 2018, 09:13
Hi,
I'm testing HRC+ system.
When i'm doing a single killConnection call, everything seems to work well and as expected on client side. logs are:
logs are:
killConnection
onConnectionRetry
onConnectionResume
Problem starts when i'm simulating a double killConnection, meaning, another killConnection before getting to Resume (by the way - would be nice to hear how rare actually this case is, and if I can be neglected).
In this case, client logs are:
killConnection
onConnectionRetry
killConnection
onConnectionResume
onConnection (AGAIN, without any disconnection)
Seems like the serverside still sends messages on the old socket, that didn't disconnect, and there's a new socket on which client now sends messages. How can this case be handled? Basically, I wouldn't mind that in those cases the HRC+ will not kick in, and the client will experience a regular disconnection.
Client side is Objective-C API version 1.7.3.
Thanks!!
Eyal Barak
I'm testing HRC+ system.
When i'm doing a single killConnection call, everything seems to work well and as expected on client side. logs are:
logs are:
killConnection
onConnectionRetry
onConnectionResume
Problem starts when i'm simulating a double killConnection, meaning, another killConnection before getting to Resume (by the way - would be nice to hear how rare actually this case is, and if I can be neglected).
In this case, client logs are:
killConnection
onConnectionRetry
killConnection
onConnectionResume
onConnection (AGAIN, without any disconnection)
Seems like the serverside still sends messages on the old socket, that didn't disconnect, and there's a new socket on which client now sends messages. How can this case be handled? Basically, I wouldn't mind that in those cases the HRC+ will not kick in, and the client will experience a regular disconnection.
Client side is Objective-C API version 1.7.3.
Thanks!!
Eyal Barak