Skip to content
This repository


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

reflect event maps from Resourceful resources

tree: edb93f28c0

Fetching latest commit…

Cannot retrieve the latest commit at this time


Reflects servers from resourceful resources. Can be used as a stand-alone module or as a Flatiron plugin.


The socketful project removes the process of writing boilerplate event mapping code for interacting with resourceful resources. socketful uses reflection to reflect a server interface that maps all events needed to perform basic real-time CRUD operations with resourceful. socketful also has the ability to expose additional arbitrary remote resource methods in

Through the removal of this boilerplate code, socketful creates a robust, standardized, and re-usable interface for any resourceful resource.

Remark: If you require RESTful HTTP routing instead of sockets, try the restful library.


 npm install socketful


Define resource(s)

var resourceful = require('resourceful'),
    Creature    = resourceful.define('creature');'type', String, { default: "dragon" });'life', Number, { default: 10, min: 0, max: 20 });

additional API documentation for defining resources

As a Flatiron Plugin

To use socketful as a Flatiron plugin you will have to:

  • Define resource(s) in your Flatiron app
  • Use the Flatiron http plugin
  • Pass the Flatiron app.server instance to socketful.createServer

Here is a code example of using socketful as a Flatiron plugin:

As a stand-alone server

To use socketful as a stand-alone server you will have to:

  • Define resource(s)
  • Create a new server based on the resource(s) using socketful.createServer

Here is a code example of using socketful as a stand-alone server:

Core Mappings

By default, socketful will map all Resourceful methods in the following signature:

server.on(resource, action, payload, callback);


socket.emit('creature', 'create', { id: 'bob' } , function(err, bob) {
  console.log('created: ', bob);
Socket       Resource     Action    Payload  Callback        Resource Method

socket.emit('creature', 'create',  data,    callback)   =>  Creature.create()
socket.emit('creature', 'get',     data,    callback)   =>  Creature.get()
socket.emit('creature', 'all',     data,    callback)   =>  Creature.all()
socket.emit('creature', 'update',  data,    callback)   =>  Creature.update()
socket.emit('creature', 'destroy', data,    callback)   =>  Creature.destroy()

The server will delegate all incoming Creature events to the resource and respond back with the appropriate result.

Exposing Arbitrary Resource Methods

In many cases, you'll want to expose additional methods on a Resource through outside of the included CRUD operations: create, all, get, update, destroy.

socketful has built in support for easily exposing arbitrary remote resource methods.

Consider the example of a Creature. We've already defined all the socketful CRUD events, but a Creature also needs to eat!

Simply create a new method on the Creature resource called feed.

Creature.feed = function (_id, options, callback) {
  callback(null, 'I have been fed');

This feed method is consider private by default, in that it will not be exposed to the web unless it's set to a remote function. To set a resource method to remote, simply:

Creature.feed.remote = true

It's easy as that! By setting the feed method to remote, the following events will exist in the server.

socket.emit('creature', 'feed', data, callback)  => Creature.feed()

Resource Security

There are several ways to provide security and authorization for accessing resource methods exposed with socketful. The recommended pattern for authorization is to use resourceful's ability for before and after hooks. In these hooks, you can add additional business logic to restrict access to the resource's methods.

TL;DR; For security and authorization, you should use resourceful's before and after hooks.


 npm test


  • Cleanup create / extend code for flatiron plugin
  • Better browser / isomorphic support via resourceful socketful engine
  • Add ability to specify schemas for remote method argument payloads
  • Improve Tests
  • Add better error support via errs library
Something went wrong with that request. Please try again.