I tried setting up a socket connection with functional session and failed, miserably. I finally figured out why, after a full day of searching (I know how bad this makes me sound at my job, ah well).

I'm not using this lib specifically, but I found the solution and the same problem in this lib. Setting cookies from xhr cross-domain won't work. You'll need a jsonp implementation or additional script tag on the page, otherwise it will not store the cookie and your session will not persist.

var script = document.createElement('script');
script.src = xOriginCookieURL;

document.getElementsByTagName('head')[0].appendChild(script);

Now just slightly modify __getcookie to call a function and you'll know when it's done (so basic jsonp). and it's solved.

I am using sails.io.js and socket.io-client on the frontend and I have configured it to reconnect if the connection is lost with the server and it is working fine. The other scenario that I want to test is mentioned below

1. Server is down intially
2. User accesses the frontend application in the browser
3. The application tries to create a socket connection to the server, but the handshake fails as the server is down

How to make the socket connection in this case (i.e. try to connect until the server is up again)

Hello @mikermcneil and team,

Is the repo for sails.io.js library not maintained anymore?
The socket support is so outdated supporting only 2.0.3. socket.io is now at 4.x

It seems there is no maintenance here. Is there any near plans to fix this repo?

Thanks!

I have a SPA which using sailjs and vuejs.
I got an issue when trying to reconect after go to a new view.
The issue is that I try to destroy all old listeners and reassign new event listener by using
io.socket.removeAllListeners();

but then I was struggling because the socket still queue old events.
Then I found out that the removeAllListeners(); methods only revoke _raw io object events but not the eventQueue object.

I managed to fix the issue by calling io.socket.eventQueue = {}.
I just wonder why the eventQueue is still remain and should I change it manually

Sails supports custom environments and will set sails.config.environment accordingly. However this lib will try to determine the environment (either development or production) based on whether the script src contains min or production. We do need the correct env in our frontend code.

Our current workaround is a custom API call.

Dear team,

We use this sails.io.js library inside Angular web app and we was wondering if there is an issue with repository or if it has been replaced. Last version is 1.2.1 released in March 2018 embeds the outdated socket.io 2.0.3.

Any reason why this repository doesn't receive any commit anymore ?

Thanks for the clarification.

Olivier.

I have authorisation token in my redux store. I want to update the header once the value is available in store.
in one file i have

import socketIOClient from 'socket.io-client';
import sailsIOCLient from 'sails.io.js';
export const baseURL = 'http://localhost:1337/';

const io = sailsIOCLient(socketIOClient);
io.sails.url = baseURL;
io.sails.initialConnectionHeaders = { nosession: true };
io.sails.transports = ['websocket'];

export { io };

and in another file I want to update header

import {io} form 'xyz.js';
io.sails.header = {authorisation : '<value from store>';
io.socket.get('\url' (resp)=>{
console.log(resp)
})

the request is sent without headers;

When I include it to my Angular project, this library
cause CPU performance waste, up to 100%.

Hello, I was wondering if there is a "sails socket io client" for C# because I develop my applications on unity. Otherwise, can we do without it?

In the sails doc:
"There are also a handful of community projects implementing Sails/Socket.IO clients for native iOS, Android, and Windows Phone."
I have not found for c#

Thank you.

[Edit]
The doc explains:

Can I bypass this client and use Socket.IO directly?

It is possible to bypass the request interpreter in your Sails app and communicate with Socket.IO directly. However, it is not reccommended, since it breaks the convention-over-configuration philosophy used elsewhere in the framework. The Sails socket client (sails.io.js) is unobtrusive: it works by wrapping the native Socket.IO client and exposing a higher-level API that takes advantage of the virtual request interpreter in Sails to send simulated HTTP requests. This makes your backend code more reusable, reduces the barrier to entry for developers new to using WebSockets/Socket.IO, and keeps your app easier to reason about.

Note: In very rare circumstances (e.g. compatibility with an existing/legacy frontend using Socket.IO directly), bypassing the request interpreter is a requirement. If you find yourself in this position, you can use the Socket.IO client, SDK, and then use sails.io on the backend to access the raw Socket.IO instance. Please embark on this road only if you have extensive experience working directly with Socket.IO, and only if you have first reviewed the internals of the sockets hook (particularly the "admin bus" implementation, a Redis integration that sits on top of @sailshq/socket.io-redis and powers Sails's multi-server support for joining/leaving rooms).

It would be really nice if there is an existing client for c#

I'm trying to do some testing, and it appears that I can't connect to my server multiple times on the same port. Is this a known issue? Here's my test:

function setupConnection (client) {
  var socketIoClient = require('socket.io-client');
  var sailsIoClient = require('sails.io.js');

  var io = sailsIoClient(socketIoClient);
  // Set some options:
  // (you have to specify the host and port of the Sails backend when using 
  // this library from Node.js)
  io.sails.transports = ['websocket'];
  // disable verbose logging
  io.sails.environment = 'production';
  // disable auto-connect, so that we can connect to multiple domains
  io.sails.autoConnect = false;

  return io.sails.connect('http://'+client.tenantDomain+':1338');
}


describe('Multitenancy', function () {
  var client = company1;
  it('should be able to connect to ' + client.tenantDomain, function (done) {
    var socket = setupConnection(client);
    socket.get('/date', function (body) {
      console.log("/date:", body)
      socket.disconnect();
      done();
    });
  });

  it('should be able to connect to ' + client.tenantDomain, function (done) {
    var socket = setupConnection(client);
    socket.get('/date', function (body) {
      console.log("/date:", body)
      socket.disconnect();
      done();
    });
  });

  client = company2;
  it('should be able to connect to ' + client.tenantDomain, function (done) {
    var socket = setupConnection(client);
    socket.get('/date', function (body) {
      console.log("/date:", body)
      socket.disconnect();
      done();
    });
  });

  it('should be able to connect to ' + client.tenantDomain, function (done) {
    var socket = setupConnection(client);
    socket.get('/date', function (body) {
      console.log("/date:", body)
      socket.disconnect();
      done();
    });
  });
});

for brevity I left out the definition of clients, but I hope you can see what I'm trying to do. All my tests after the first timeout, and debugging shows that the sockets are in a disconnected state.

Also, FWIW, the docs in the README.md show passing the URL as a part of the (single) options object, but it's actually the first parameter, and options are the second. tripped me up for a bit.

Because the socket session id is set as a SameSite None cookie without secure, it gets removed by Firefox.

This means this entire library does not work with current versions of Firefox when the frontend client is hosted separately from the backend sails.js framework.

Pls fix this..

Hey! My old project used io.socket.get to connect to secret rooms.

io.socket.get('/list/handshake', function (data, jwr) {
if (jwr.error) {
return;
}
});

io.socket.get('/terminal/handshake', function (data, jwr) {
if (jwr.error) {
return;
}
});

After auditing the packages, I received updates and am now getting a 401 error when trying to connect.

I'm assuming that it's necessary to pass cookie bitches and the io.socket.request method is more suitable for this, but I have a poor idea of what exactly the sails require to pass the request authorization. Who faced a similar problem and what solution can work?

io.socket.request({
method: 'get',
url: '/list/handshake',
headers: {
// cookie: document.cookie,
'x-csrf-token': window.SAILS_LOCALS._csrf ? window.SAILS_LOCALS._csrf : '',
}
}, function (data, jwr) {
if (jwr.error) {
return;
}
});

io.socket.request({
method: 'get',
url: '/terminal/handshake',
}, function (data, jwr) {
if (jwr.error) {
return;
}
});