Ufdjrw

How can I prevent/balance waiting and turtling as a response to cooldown mechanics

Did any compiler fully use 80-bit floating point?

Sally's older brother

AppleTVs create a chatty alternate WiFi network

Resize vertical bars (absolute-value symbols)

One-one communication

Why is it faster to reheat something than it is to cook it?

Co-worker has annoying ringtone

Universal covering space of the real projective line?

Can an iPhone 7 be made to function as a NFC Tag?

what is the log of the PDF for a Normal Distribution?

Did Mueller's report provide an evidentiary basis for the claim of Russian govt election interference via social media?

Does silver oxide react with hydrogen sulfide?

As a dual citizen, my US passport will expire one day after traveling to the US. Will this work?

How much damage would a cupful of neutron star matter do to the Earth?

Was Kant an Intuitionist about mathematical objects?

Putting class ranking in CV, but against dept guidelines

Why is std::move not [[nodiscard]] in C++20?

My mentor says to set image to Fine instead of RAW — how is this different from JPG?

A `coordinate` command ignored

The Nth Gryphon Number

Mounting TV on a weird wall that has some material between the drywall and stud

Where is the Next Backup Size entry on iOS 12?

What would you call this weird metallic apparatus that allows you to lift people?

Socket.io event listener not working on server side

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;

1

0

I am using socket IO rooms in my project.

On the server side:

const PORT = 4200

const server = require('http').createServer(require('express')())
const io = require('socket.io')(server)

server.listen(PORT)

const room = 'example' 

io.sockets.on('connection', (socket) => 
 socket.join(room); 
);

From emit data from a server to client, I am using io.sockets.in(room).emit(path, data) and it works perfectly.

The problem is when I listen for events from the client side that code is not fired.

io.sockets.on(path, () => console.log('FIRED'))

The path is definitely correct.

What is wrong? Am I using the on event incorrect?

node.js websocket socket.io

share|improve this question

edited Mar 9 at 4:11

Dale Burrell

3,50252655

asked Mar 8 at 23:16

cijowabehcijowabeh

62

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Hey. It seems a lot of the code is missing. Can you provide a minimal, complete example of the code that is not working?
  
  – Markus
  Mar 8 at 23:46
  
  

  
  
  
  

add a comment | 

1

0

I am using socket IO rooms in my project.

On the server side:

const PORT = 4200

const server = require('http').createServer(require('express')())
const io = require('socket.io')(server)

server.listen(PORT)

const room = 'example' 

io.sockets.on('connection', (socket) => 
 socket.join(room); 
);

From emit data from a server to client, I am using io.sockets.in(room).emit(path, data) and it works perfectly.

The problem is when I listen for events from the client side that code is not fired.

io.sockets.on(path, () => console.log('FIRED'))

The path is definitely correct.

What is wrong? Am I using the on event incorrect?

node.js websocket socket.io

share|improve this question

edited Mar 9 at 4:11

Dale Burrell

3,50252655

asked Mar 8 at 23:16

cijowabehcijowabeh

62

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Hey. It seems a lot of the code is missing. Can you provide a minimal, complete example of the code that is not working?
  
  – Markus
  Mar 8 at 23:46
  
  

  
  
  
  

add a comment | 

I am using socket IO rooms in my project.

On the server side:

const PORT = 4200

const server = require('http').createServer(require('express')())
const io = require('socket.io')(server)

server.listen(PORT)

const room = 'example' 

io.sockets.on('connection', (socket) => 
 socket.join(room); 
);

From emit data from a server to client, I am using io.sockets.in(room).emit(path, data) and it works perfectly.

The problem is when I listen for events from the client side that code is not fired.

io.sockets.on(path, () => console.log('FIRED'))

The path is definitely correct.

What is wrong? Am I using the on event incorrect?

node.js websocket socket.io

share|improve this question

edited Mar 9 at 4:11

Dale Burrell

3,50252655

asked Mar 8 at 23:16

cijowabehcijowabeh

62

const PORT = 4200

const server = require('http').createServer(require('express')())
const io = require('socket.io')(server)

server.listen(PORT)

const room = 'example' 

io.sockets.on('connection', (socket) => 
 socket.join(room); 
);

io.sockets.on(path, () => console.log('FIRED'))

share|improve this question

edited Mar 9 at 4:11

Dale Burrell

3,50252655

asked Mar 8 at 23:16

cijowabehcijowabeh

62

share|improve this question

edited Mar 9 at 4:11

Dale Burrell

3,50252655

asked Mar 8 at 23:16

cijowabehcijowabeh

62

edited Mar 9 at 4:11

Dale Burrell

3,50252655

edited Mar 9 at 4:11

Dale Burrell

3,50252655

asked Mar 8 at 23:16

cijowabehcijowabeh

62

asked Mar 8 at 23:16

cijowabehcijowabeh

62