Loopback with socketio

[Matthew Williams]

I would like to use socketio in my loopback server app.  What's the best way to require it.  I am looking for the socket server to run on port 80 along with my loopback server.   Following the socketio example I would use the express app like below:

var app = require('express')();

var http = require('http').Server(app);

var io = require('socket.io')(http);

Should I add this into the loopback.js file or is there already a configuration I can use with the loopback application to achieve this.

[Miroslav Bajtoš]

I'll assume you already have app = loopback(); and you configured all models and middleware.

Now you need to replace the call to app.listen() with the following:

// original code - no socket.io

app.listen()

// new code - add socket.io to the mix
var server = require('http').Server(app);

var io = require('socket.io')(server);

server.listen(app.get('port'), app.get('host'));

Let me know if that works for you.

Miroslav

[Raymond Feng]

It could be even simpler:

var server = app.start();

var io = require(‘socket.io’)(server);

Thanks,

---

Raymond Feng

Co-Founder and Architect @ StrongLoop, Inc.

StrongLoop makes it easy to develop APIs in Node, plus get DevOps capabilities like monitoring, debugging and clustering.

--
You received this message because you are subscribed to the Google Groups "LoopbackJS" group.
To unsubscribe from this group and stop receiving emails from it, send an email to loopbackjs+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Ritchie Martori]

If you used `slc lb project` to scaffold your app, in your app.js on line ~ 126, you should be able to reference the `http` Server object by doing this:

```js

app.start = function() {

  var http = app.listen(function() {

    // ...

  });

  require('socketio')(http);

};

```

--

[Matthew Williams]

Here is what I did:

var server = http.createServer(app);

 /*

  * Push notifications added

  */

app.io = require('socket.io').listen(server);

I attached io to the app object.  Now I am trying to get a reference to my model instances in a beforeSave hook.  So I can emmit an event with socket i.o.  For example in a product model:

//models/product.js  

Product.beforeSave = function(callback){

console.log("beforeSave");

console.log(callback);

app.io.emmit("productInfo", "my model instance attributes....")

}

How do I reference the model instance from the beforeSave.  I can use afterSave as well I just don't understand how to get the values of the model in the callback.  In the above example the model properties are configured in "models.json".

Thanks.

[Matthew Williams]

Okay I see the context of the callback is the model instance.  I just use the keyword this to get my model attributes:  this.price etc...

On Wednesday, June 25, 2014 6:56:56 PM UTC-5, Matthew Williams wrote:

[Charles Soetan]

in my server.js I did this

if (require.main === module) {

  // app.start();

  var server = require('socket.io')(app.start()); // I replace the app.start() with this

}

How do I now use the socket in my boot folder.

Thanks

[Miroslav Bajtoš]

On Fri, Sep 19, 2014 at 1:19 AM, Charles Soetan <caso...@gmail.com> wrote:

in my server.js I did this

if (require.main === module) {

  // app.start();

  var server = require('socket.io')(app.start()); // I replace the app.start() with this

}

I'd say you have to store your socket.io server on the app object, as was shown in earlier in this thread.

if (require.main === module) {

  app.io = require('socket.io')(app.start());

}

Then you can use `app.io` to access the socket.io server.

Note that the socket.io server is not available at the time your `boot/*.js` are run.

Miroslav

[Charles Soetan]

thanks.

[jmls]

does anyone have an example of how to use socket.io in loopback ?

I have followed all the above examples, it seems to be available, but whenever I try to connect from a client I just get a "disconencted" message

so. my code looks like this

if (require.main === module) {

  app.io = require('socket.io')(app.start());

where would / should I put the 

io.on('connection'

?

thanks

[Alexander Makarenko]

Why not add boot script with something like following:

// boot/io.js

module.exports = function(app) {

  app.on('started', function() {

    require('./io')(app, app.io);

  });

}

// boot/io/index.js

module.exports = function(app, io) {

  require('./chat')(app, io);

}

// boot/io/chat.js

module.exports = function(app, io) {

  io.on('connection', function(socket) {

    // functionality HERE

  });

[Alexander Makarenko]

Sorry for mistake in code: require('./io')(app, app.io) may not work because io.js is already required.

--
You received this message because you are subscribed to a topic in the Google Groups "LoopbackJS" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/loopbackjs/6qpQwggf2_c/unsubscribe.
To unsubscribe from this group and all its topics, send an email to loopbackjs+...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Sincerely,

Alexander Makarenko

Curriculum vitae: http://liberitas.info/cv

Cell.: +7 988 517 0645

Skype: estliberitas

[Miroslav Bajtoš]

On Tue, Oct 7, 2014 at 12:50 AM, Alexander Makarenko <estlib...@gmail.com> wrote:

Why not add boot script with something like following:

// boot/io.js

module.exports = function(app) {

  app.on('started', function() {

    require('./io')(app, app.io);

  });

}

To my best knowledge, this will not work, because `app` is a request handler function, but `socket.io` requires an instance of `http.Server` instead.

Miroslav 

[Alexander Makarenko]

You are right. I posted wrong code. Here is working one:

// server/server.js

...

if (require.main === module) {

  app.server = app.start()

}

// boot/io.js

module.exports = function(app) {

  app.on('started', function() {

    app.io = require('socket.io').listen(app.server)

    require('./io')(app, app.io);

  });

}

[jmls]

thanks for this - it works ... but .. ;)

how do I refer to app.io in my model ? I am wanting to emit a message on an update, so I am hooking into the afterSave()

module.exports = function (Salesrep) {

 Salesrep.afterSave = function(next) {

     app.io.to("data:salesrep").emit( "afterUpdate", { body: this } )

   }

however, obviously, app is not defined

Julian

[Miroslav Bajtoš]

On Fri, Oct 24, 2014 at 12:27 PM, jmls <jul...@dotr.com> wrote:

thanks for this - it works ... but .. ;)

how do I refer to app.io in my model ? I am wanting to emit a message on an update, so I am hooking into the afterSave()

module.exports = function (Salesrep) {

 Salesrep.afterSave = function(next) {

     app.io.to("data:salesrep").emit( "afterUpdate", { body: this } )

   }

module.exports = function (Salesrep) {

 Salesrep.afterSave = function(next) {

   Salesrep.app.io.to("data:salesrep").emit( "afterUpdate", { body: this });

   next();

 };

}

See [1] and [2] for more details.

Don't forget to call `next` in your custom method.

Miroslav

[1] http://stackoverflow.com/questions/26457327/how-do-i-get-a-hold-of-a-strongloop-loopback-model/26543620#26543620 and  

[2] https://groups.google.com/forum/#!topic/loopbackjs/Z5VNL5Aw4Cs

[Alexander Makarenko]

Just read docs. For example, here: Migrating apps to version 2.0

So you'll find application object is available as app property of model:

And your example will look like...

module.exports = function (Salesrep) {
  Salesrep.afterSave = function(next) {

    Salesrep.app.io.to("data:salesrep").emit( "afterUpdate", { body: this } )
  }
  ...
}

Or if you want to use access Salesrep.app as variable, you have to setup model inside model's attached listener:

module.exports = function (Salesrep) {
 Salesrep.on('attached', function() {
   var app = Salesrep;

   Salesrep.afterSave = function(next) {
     app.io.to("data:salesrep").emit( "afterUpdate", { body: this } )
   }
   }

   ...
 })
}

[jmls]

Thanks a lot Miroslav, that seems to work for me.

however, even if I get a list of connected clients to the room (sending to  [ X3Es6HDM9U61ItstAAAB: true ]

) , they never receive the message

console.log("sending to ",Salesrep.app.io.sockets.adapter.rooms["data:customer"]);

     

Salesrep.app.io.sockets.to("data:customer").emit( "data")

i've tried 

sockets.to("

sockets.in("

.emit and .send ;)

[jmls]

fwiw, this works for me

{model}.app.io.sockets.in("toRoom").emit("someMessage",{yourMessageBody})

julian

[Kevin Sproles]

For me, doing this worked:

  app.io = require('socket.io')(app.start());

But in my hooks (i.e. .afterCreate or .afterUpdate) I can't get any of the examples from this thread to work. I instead used:

Salesrep.app.io.emit( "salesrep:save", this)

[Felipe Figueroa]

Doing this

app.io = require('socket.io')(app.start());

would lead  for socket io to answer instead of loopback, or it wouldl listen on another port?

I'm confused about what will happen to the default endpoints and verbs if you run socket.io along with loopback.

[Maker Su]

Here is my example, https://github.com/makersu/loopbackchat

Felipe Figueroa於 2014年12月4日星期四UTC+8下午8時07分00秒寫道：

[Felix Itzenplitz]

Hi, this is my implementation of integrating socket.io into loopback:

https://github.com/loggrio/loggr-api/blob/socket.io/server/server.js

It allows you to separate all socket.io stuff into a .js file in your boot/ folder.

https://github.com/loggrio/loggr-api/blob/socket.io/server/boot/socket.js

[Felipe Figueroa]

It makes every bit of sense. However, I'm getting error 400. I believe I should add upgrade headers through nginx, but can't seem to get it right.