Skip to content

Fix to manage namespace disconnection and reconnection#1296

Closed
ifraixedes wants to merge 1 commit intosocketio:0.9from
ifraixedes:0.9
Closed

Fix to manage namespace disconnection and reconnection#1296
ifraixedes wants to merge 1 commit intosocketio:0.9from
ifraixedes:0.9

Conversation

@ifraixedes
Copy link

Hi,

I was struggling to manage the namespace client disconnection in the application that we are working.
I realised that when the client disconnect from a namespace, after if I tried to connect again to the same namespace, it didn't receive the messages from the server, at least if the client reconnected the socket to the same namespace some seconds after he had disconnected it.

After debugging the code for awhile, I found this fix.

This pull request corresponds to another pull request to socket.io-client that I've done: #568

By the way, I also realised that if I would like to manage a disconnection to a namespace, emitted by the client I have to listen the 'disconnect' event and manage the first call checking if the message is 'packet' and in that case call the method 'disconnect()' from the socket; next the piece of code to do that:

var io = require('socket.io').listen(80);
var chat = io
    .of('/chat')
    .on('connection', function (socket) {
        socket.on('disconnect', function (msg) {
            if (msg === 'packet') {
                socket.disconnect();
            }
        });
    });

…disconnect the socket from a namespace no the global socket) and release the attached socket's event listeners
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant