Databases
StackOverflow2013
Postsdbo
POSimple chat with socket.io
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSimple chat with socket.io
    primarykey
    data
    text
    <p>I'm trying to implement a very simple chat with socket.io, and i'm getting into a really weird problem.</p> <p>server side:</p> <pre><code>var users = {}; io.sockets.on('connection', function (socket) { socket.on('join', function(userNameParam) { socket.join('chatchannel'); users[userNameParam] = userNameParam; socket.userName = userNameParam; socket.emit('firstLogin',users); socket.broadcast.to('chatchannel').emit('addConnectedUser',userNameParam); }); }); </code></pre> <p>client side:</p> <pre><code>var socket = io.connect(); function onLogInLogOutClick() { var userName = document.getElementById("txtUserName").value; // get button text var btnLogInLogOut = document.getElementById('btnLogInLogOut'); var txtBtnLogInLogOut = btnLogInLogOut.textContent || btnLogInLogOut.innerText; if(txtBtnLogInLogOut == 'LogIn') { // send join message socket.emit('join', userName); } } </code></pre> <p>When I login in the first browser tab (for the first user) everything works great, but when I login in the second browser tab (for the second user), for some unknown reason 'join' event on the server side gets called more than once!</p> <p>I've read on the API that 'socket.emit' suppose to raise the event only for the current request socket client, so what can be the issue ?</p> <p><strong>UPDATE:</strong></p> <p>I looked at the socket.id on the first and second call, and it's the same. why does it happen?</p> <p><strong>UPDATE 2:</strong></p> <p>On the second tab, when reaching to the server side, I see that the request socket is subscribing TWICE to each event. I don't know why.</p> <p><strong>UPDATE 3:</strong></p> <p>Found the problem: server code was placed here:</p> <pre><code>module.exports = function(app, socketio, loggerInstance) { io = socketio; app.get('/chat',chat); }; var chat = function(req, res){ *** SERVER CODE THAT WAS WRITTEN ABOVE *** res.render('chat'); }; </code></pre> <p>I moved the server code to 'app.js' file and it works fine.</p> <p>Still I can't figure out why those events were called more than once.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USohadinho
    1. USohadinho
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. POSimple chat with socket.io
      1. USJasonM
      1. VTFavorite
    1. COkinda strange... is it possible that `onLogInLogOutClick()` is being called twice in the same tab? have you tried `socket.on('connect',...)` just for testing when a socket connects? which browser are you using?
      singulars
      1. POSimple chat with socket.io
      1. USSalvatorelab
    2. COno way.. that's what's strange to me. Right after it loads the page - it registers twice to the event.
      singulars
      1. POSimple chat with socket.io
      1. USohadinho
    3. COAre you sure the join event is happening more than once? I did a quick test with the code you have, at least something very similar, and it only roins the actual event once. In the debug log it does look like it logs the write for each connected client, not sure why or if that is expected functionality. That being said it did only run once. Could you do a console.log in the `join` and then paste your logs?
      singulars
      1. POSimple chat with socket.io
      1. USJasonM
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload