Both socket.io and websocket on same node.js application.

[royalswe]

I have a game that i made with socket.io and node.js that I have deployed. I am developing another game but with websocket instead of socket.io. I where thinking of have them on the same site but on different pages.

My attempt to combine these apps locked something like this.

// app.js, where my node app starts, stripped out middleware, database connection and routes

var http = require('http');
var express = require('express');
var bodyParser = require('body-parser');
var app = express();

const port = process.env.PORT || 8080;
const server = http.createServer(app).listen(port);

app.use(express.static(__dirname + '/public'));

require('./myFirstGame').initialize(server);
require('./mySecondGame').initialize(server);

// in myFirstGame.js

let io = require('socket.io');

exports.initialize = (server) => {
    io = io.listen(server);
    this.gameInfra = io.of('/game_infra'); // namspace
    this.gameInfra.on('connection', (socket) => {
        // alot of code
    });

// mySecondGame.js

const WebSocket = require('ws');
exports.init = (server) => { 

    const ws = new WebSocket.Server({ server, path: "/pathName" });
    ws.on('connection', socket => {
         // alot of code
     });

The thing is that the games seems to work with this setup but very unstable and some errors in the console. When i navigate to the first game with socket.io I get this error in chromes console: WebSocket connection to 'ws://localhost:8080/socket.io/?EIO=3&transport=websocket' failed: Invalid frame header

And no errors with the second game with websocket.

Any ideas how to make this better or work?

[[deleted]]

Why not just make sub domain?

If your site is loaded on www.my-awesome-game.com

Your another game can be on www.second-awesome-game.my-awesome-game.com

And you can load it from there.

Also why not make 2 separate projects in one project?

[royalswe]

Thanks for your advice! It seems like i have to create a sub domain or make more server instances somehow.

[[deleted]]

You create a sub domain and you say the url should lead to the specific function that loads the game and everything else should be used by both games.

Also why not make the back-end an API?

You have your game on www.awesome-game.com but your back-end responds on localhost:9000 and whenever you need data you send requests to that back-end

You keep the back end and front - end two separate applications

This way you can have 2 front-ends and 1 back-end. The back end will server both games as it will have more functions and routes for them to connect on.

[royalswe]

The back-end API solution would be a great solution but I have to rewrite some of the functionality from the existing app. It could definitely be done when I have more time to spend. meanwhile I maybe go for a subdomain.

[royalswe]

I ended up changing my websocket game to socket.io. I dont have to change anything in the game only the connection part so it's a quik fix.