The Issues First of all you need to be looking at the server port that the server is bound on (app.listen(3001);) on the client side in order to reach the server at all. As for socket.io, adding http://localhost:3001 before the rest of the source in the link tag solves this problem. This is apparently due … Read more
Yes, you can use the same port number for both TCP and UDP. Many protocols already do this, for example DNS works on udp/53 and tcp/53. Technically the port pools for each protocol are completely independent, but for higher level protocols that can use either TCP or UDP it’s convention that they default to the … Read more
With socket.emit you can register custom event like that: server: var io = require(‘socket.io’).listen(80); io.sockets.on(‘connection’, function (socket) { socket.emit(‘news’, { hello: ‘world’ }); socket.on(‘my other event’, function (data) { console.log(data); }); }); client: var socket = io.connect(‘http://localhost’); socket.on(‘news’, function (data) { console.log(data); socket.emit(‘my other event’, { my: ‘data’ }); }); Socket.send does the same, but … Read more
Based on your question: My question is, using the code below, how would you be able to have multiple clients connected? I’ve tried lists, but I just can’t figure out the format for that. How can this be accomplished where multiple clients are connected at once and I am able to send a message to … Read more
Explanation: This problem occurs because Chrome allows up to 6 open connections by default. So if you’re streaming multiple media files simultaneously from 6 <video> or <audio> tags, the 7th connection (for example, an image) will just hang, until one of the sockets opens up. Usually, an open connection will close after 5 minutes of … Read more
It looks like what you are looking for is an graceful shutdown. First your code does not work because you are closing socket immediately after calling shutdown. The rule is that in a graceful shutdown, both sides must be aware of the shutting down and have acknowledged it before any actually closes the socket. I … Read more
The connection should remain open regardless but yes it’s often common to see protocols implement a heartbeat in order to help detect dead connections, IRC with the PING command for example.
When you send bytes from a buffer with a normal TCP socket, the send function returns the number of bytes of the buffer that were sent. If it is a non-blocking socket or a non-blocking send then the number of bytes sent may be less than the size of the buffer. If it is a … Read more
To answer your questions. Even though they achieve (in general) similar things, yes, they are really different. WebSockets typically run from browsers connecting to Application Server over a protocol similar to HTTP that runs over TCP/IP. So they are primarily for Web Applications that require a permanent connection to its server. On the other hand, … Read more
Nikolai, using a separate socket and bind(2) for each address or messing with routing tables is often not a feasible option e.g. with dynamic addresses. A single IP_ADDRANY-bound UDP server should be able to appear to respond on the same dynamically-assigned IP address a packet is received on. Luckily, there is another way. Depending on … Read more