iOS - ConnectandLogin - onConnectionClosedEvent

[nekinpatel]

Hi

i am trying with connectandlogin example ; tested with below scenario.

1. added onConnectionClosedEvent listener
2. implemented method required for above listener
3. now when i run example , it connects user successfully and login also.
4. but at time of closing ESSever manually.... it is not throwing any event to listener of connection closed.

Any idea ? [ we do not prefer to have timer in place for this]

Thanks

[tcarr]

Are you closing the ES5 server before the user logs in or afterward? You won't get a ConnectionClosedEvent if the original connection fails due to the ES5 server not being reached.

[nekinpatel]

No. I am not closing the connection before connecting or login. And also, the user is connected and logged in successfully. What could be the problem?

Simply I have added the listener immediate after the two listeners (for connection response and login response).

But it doesn't get called, when I stop the server manually.

Thanks for prompt reply.

[tcarr]

If you are using the same syntax as the other listeners, then this sounds like a bug in our api. I'll add a ticket to our system about it.

edit: which version of the ES5 client api are you using?

[nekinpatel]

Yes syntax is same like other listeners. We are using 5.3.2 API for cocoa touch.

[tcarr]

Thanks! I'll let Jason know it's 5.3.2.

[nekinpatel]

Can we know that if it is bug then how much time it will take to get resolved ?

[tcarr]

How much time it will take for a fix depends on the type of bug, assuming Jason reproduces it. I'll let you know when we have a beta build of the updated api.

[tcarr]

Jason was unable to reproduce this error using the ES5.3.2 iOS client api, and an ES5.3.2 server. This is the code that he added to the example:

[es.engine addEventListenerWithTarget:self action:@selector(onConnectionClosed:) eventIdentifier:EsMessageType_ConnectionClosedEvent];

- (void) onConnectionClosed:(EsConnectionClosedEvent*) event {
    DLOG(@"onConnectionClosed");
}

And here are the logs that he saw during testing, starting with the successful LoginResponse:

2012-07-02 10:45:38.241 cocoa-touch-tests[18681:f803] -[EsManagerHelper onLoginResponse:]: onLoginResponse
2012-07-02 10:45:38.242 cocoa-touch-tests[18681:f803] -[EsUserManager addUser:]: addUser
2012-07-02 10:45:38.242 cocoa-touch-tests[18681:f803] Login Accepted: true
2012-07-02 10:45:38.243 cocoa-touch-tests[18681:f803] -[EsEngine checkMessageOrder:connection:]: Queued messages 0
2012-07-02 10:45:46.612 cocoa-touch-tests[18681:f803] -[EsSocketConnection stream:handleEvent:]: stream handleEvent 2
2012-07-02 10:45:46.617 cocoa-touch-tests[18681:f803] -[EsSocketConnection stream:handleEvent:]: NSStreamEventHasBytesAvailable
2012-07-02 10:45:46.617 cocoa-touch-tests[18681:f803] -[EsSocketConnection stream:handleEvent:]: stream handleEvent 16
2012-07-02 10:45:46.618 cocoa-touch-tests[18681:f803] -[EsSocketConnection stream:handleEvent:]: NSStreamEventEndEncountered
2012-07-02 10:45:46.621 cocoa-touch-tests[18681:f803] -[cocoa_touch_testsAppDelegate onConnectionClosed:]: 
onConnectionClosed