View our GitHub

Please visit sails-docs on GitHub to view documentation on your mobile device.

Edit Page

Resourceful PubSub


For apps that rely heavily on real-time client-server communication--for example, peer-to-peer chat and social networking apps--sending and listening for socket events can quickly become overwhelming. Sails helps smooth away some of this complexity by introducing the concept of resourceful pubsub (Publish / Subscribe). Every model (AKA resource) in your app is automatically equipped with class methods which provide a conventional, data-centric interface for both broadcasting notifications and subscribing sockets to notifications about individual database records being created, updated, or destroyed.

If you’re app is currently using the Blueprint API, you are already using resourceful pubsub methods! They are embedded in the default blueprint actions bundled with Sails, and called automatically when those actions run; causing requesting sockets to be subscribed when data is fetched and messages to be broadcasted to already-subscribed sockets when data is changed.

But even when writing custom code, you can call the methods described in this section manually in lieu of using sails.sockets.* methods directly. Think of resourceful pubsub methods as a way of standardizing the interface for socket communication across your application: things like the names for rooms, the schema for data transmitted as socket messages, and the names of socket events. These methods are designed exclusively for scenarios where one or more user interfaces are listening to socket events as a way of keeping in sync with the backend. If that does not fit your use case or if you are having trouble deciding, don't worry; just call sails.sockets.broadcast(), sails.sockets.join(), or sails.sockets.leave() directly instead. It is perfectly acceptable to use either approach, or even both approaches in the same app.

Listening for events on the client

While you are free to use any Javascript library to listen for socket events on the client, Sails provides its own socket client called as a convenient way to communicate with the Sails server from any web browser or Node.js process that supports Using the Sails socket client makes listening for resourceful pubsub events as easy as:

io.socket.on('<model identity>', function (event) {

The model identity is typically the lowercased version of the model name, unless it has been manually configured in the model file.


Let’s say you have a model named User in your app, with a single “name” attribute. First, we’ll add a listener for “user” events:

io.socket.on('user', function(event){console.log(event);})

This will log any notifications about User models to the console. However, we won’t receive any such messages until we subscribe to the existing User records (aka model instances). If your app currently has the blueprint API enabled, you can use the client to watch the User model for new records, as well as subscribing to the returned set of records by making a socket GET request from the client to /user:

io.socket.get("/user", function(resData, jwres) {console.log(resData);})

This requests the current list of users from the Sails server, and subscribes the client to events about each user. Additionally, if the autoWatch setting is on (the default), the client will also be notified whenever a new User is created, and will automatically be subscribed to the new user. The callback in this example simply logs the user list to the console. See the socket.get reference for more info about this method.

It’s important to note that in order for the subscription to take place, the /user request must be made via a websocket call, not a regular HTTP request. That is, using an AJAX request (e.g. jQuery.get("/user")) will not result in the client being subscribed to resourceful pubsub messages about User. However, once the subscription is made, any changes to models--whether they be the result of a socket call, an AJAX request, even a cURL request from the command line--will cause the client to receive a notification. Continuing with the above example, if you were to open up a new browser window and go to the following URL:


You would see something like the following in the console of the first window:

    data: {
        createdAt: "2014-08-01T05:50:19.855Z"
        id: 1
        name: "joe"
        updatedAt: "2014-08-01T05:50:19.855Z"
    id: 1,
    verb: "created"

The verb indicates the kind of action that occurred. The id refers to the instance that the action occurred on, and data contains more information about the User that was acted upon. Each event type sends back slightly different information; see the individual resourceful pubsub method reference documents for more info.

Is something missing?

If you notice something we've missed or could be improved on, please follow this link and submit a pull request to the sails-docs repo. Once we merge it, the changes will be reflected on the website the next time it is deployed.


We wrote a book!

Get early access to the book
with promotion code: mcneildoc

Get the Book