Need way to distinguish server disconnects from client disconnects

[thully]

I'm using the socket.io library in my iOS app, and want to always maintain a connection as long as the app is active, automatically reconnecting after every disconnect . I can do this adding a disconnect handler that reconnects like the following:

socket.on(clientEvent: .disconnect) { args, ack in
self.socket.connect()
}

While this works, it seems that the handler is called for both disconnects due to external causes and disconnects initiated manually (i.e. by calling socket.disconnect()). While you can set flags/remove listeners every time one explicitly calls disconnect, It would be nice to have an easier way of distinguishing these built into the API.

[nuclearace]

Duplicate of #679.

[nuclearace]

Hm, actually that issue is similar, but not the same.

[2fours]

This is how I do it for now (v13.2.0) until there's concrete status codes or something:

[self.socket.defaultSocket on:@"disconnect" callback:^(NSArray * data, SocketAckEmitter * ack) {
    //server disconnect seems to yield data of "Socket Disconnected" vs client with "Disconnect" so only attempt reconnect when server disconnects
    id object0 = [data objectAtIndex:0];
    if ([object0 isEqualToString:@"Socket Disconnected"]) {
        [self reconnect];
    }
}];