socket.io with react router
I have set up a localhost socket as below:-
var http = require('http');
var server = http.createServer();
var socket_io = require('socket.io');
server.listen(4000);
var io = socket_io();
io.attach(server);
io.on('connection', function(socket){
console.log("Socket connected: " + socket.id);
socket.on('action', (action) => {
console.log('Got data!', action.message);
socket.emit('action', {type:'self', content:action.message});
});
});
and in the react component, I did this:-
import io from '../socket/connect';
class Hello extends Component {
constructor(props){
super(props);
io.on('action', (data) => {
console.log(data);
});
}
}
if this route is load 1 time, everything is perfect : socket gives 1 console log, and the react page also gives 1 console log.
However, in the react app, when I change to another route and return back, now the socket gives 1 console log, while the react page gives 2 console logs of the same message of the socket...
when I change to another route and return back again, now the socket gives 1 console log, while the react page gives 3 console logs of the same message of the socket...
I guess, whenever I access this react page, it connects to socket +1 time, so even when the socket only emits 1 message, the react page will do it many times.
How shall I improve it?
P.S. : I am also using react-router-redux for route change
reactjs socket.io
asked Nov 19 '18 at 7:20
user3836484user3836484
296
add a comment |
I have set up a localhost socket as below:-
var http = require('http');
var server = http.createServer();
var socket_io = require('socket.io');
server.listen(4000);
var io = socket_io();
io.attach(server);
io.on('connection', function(socket){
console.log("Socket connected: " + socket.id);
socket.on('action', (action) => {
console.log('Got data!', action.message);
socket.emit('action', {type:'self', content:action.message});
});
});
and in the react component, I did this:-
import io from '../socket/connect';
class Hello extends Component {
constructor(props){
super(props);
io.on('action', (data) => {
console.log(data);
});
}
}
if this route is load 1 time, everything is perfect : socket gives 1 console log, and the react page also gives 1 console log.
However, in the react app, when I change to another route and return back, now the socket gives 1 console log, while the react page gives 2 console logs of the same message of the socket...
when I change to another route and return back again, now the socket gives 1 console log, while the react page gives 3 console logs of the same message of the socket...
I guess, whenever I access this react page, it connects to socket +1 time, so even when the socket only emits 1 message, the react page will do it many times.
How shall I improve it?
P.S. : I am also using react-router-redux for route change
reactjs socket.io
asked Nov 19 '18 at 7:20
user3836484user3836484
296
add a comment |
I have set up a localhost socket as below:-
var http = require('http');
var server = http.createServer();
var socket_io = require('socket.io');
server.listen(4000);
var io = socket_io();
io.attach(server);
io.on('connection', function(socket){
console.log("Socket connected: " + socket.id);
socket.on('action', (action) => {
console.log('Got data!', action.message);
socket.emit('action', {type:'self', content:action.message});
});
});
and in the react component, I did this:-
import io from '../socket/connect';
class Hello extends Component {
constructor(props){
super(props);
io.on('action', (data) => {
console.log(data);
});
}
}
if this route is load 1 time, everything is perfect : socket gives 1 console log, and the react page also gives 1 console log.
However, in the react app, when I change to another route and return back, now the socket gives 1 console log, while the react page gives 2 console logs of the same message of the socket...
when I change to another route and return back again, now the socket gives 1 console log, while the react page gives 3 console logs of the same message of the socket...
I guess, whenever I access this react page, it connects to socket +1 time, so even when the socket only emits 1 message, the react page will do it many times.
How shall I improve it?
P.S. : I am also using react-router-redux for route change
reactjs socket.io
asked Nov 19 '18 at 7:20
user3836484user3836484
296
I have set up a localhost socket as below:-
var http = require('http');
var server = http.createServer();
var socket_io = require('socket.io');
server.listen(4000);
var io = socket_io();
io.attach(server);
io.on('connection', function(socket){
console.log("Socket connected: " + socket.id);
socket.on('action', (action) => {
console.log('Got data!', action.message);
socket.emit('action', {type:'self', content:action.message});
});
});
and in the react component, I did this:-
import io from '../socket/connect';
class Hello extends Component {
constructor(props){
super(props);
io.on('action', (data) => {
console.log(data);
});
}
}
if this route is load 1 time, everything is perfect : socket gives 1 console log, and the react page also gives 1 console log.
However, in the react app, when I change to another route and return back, now the socket gives 1 console log, while the react page gives 2 console logs of the same message of the socket...
when I change to another route and return back again, now the socket gives 1 console log, while the react page gives 3 console logs of the same message of the socket...
I guess, whenever I access this react page, it connects to socket +1 time, so even when the socket only emits 1 message, the react page will do it many times.
How shall I improve it?
P.S. : I am also using react-router-redux for route change
reactjs socket.io
reactjs socket.io
asked Nov 19 '18 at 7:20
user3836484user3836484
296
asked Nov 19 '18 at 7:20
user3836484user3836484
296
asked Nov 19 '18 at 7:20
user3836484user3836484
296
asked Nov 19 '18 at 7:20
user3836484user3836484
296
asked Nov 19 '18 at 7:20
user3836484user3836484
296
296
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53369973%2fsocket-io-with-react-router%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53369973%2fsocket-io-with-react-router%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
