CometD server for NodeJS
Clone or download
sbordet Added test for duplicate /meta/connect.
Signed-off-by: Simone Bordet <simone.bordet@gmail.com>
Latest commit e858555 Oct 31, 2018
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
test Added test for duplicate /meta/connect. Oct 31, 2018
LICENSE Initial commit Apr 5, 2017
README.md Updated README with section about contextual information. Oct 15, 2018
cometd-nodejs-server.js Added test for duplicate /meta/connect. Oct 31, 2018
package.json Updated version to 1.0.3. Jul 5, 2018

README.md

The CometD Project

CometD NodeJS Server

Server side APIs and implementation of the Bayeux Protocol for the NodeJS environment. WebSocket not (yet) supported.

NPM Installation

npm install cometd-nodejs-server

Running the tests

npm install mocha
npm install cometd
npm install cometd-nodejs-client
npm test

Minimal Application

var http = require('http');

var cometd = require('cometd-nodejs-server');
var cometdServer = cometd.createCometDServer();

var httpServer = http.createServer(cometdServer.handle);
httpServer.listen(0, 'localhost', function() {
    // Your application code here.
});

Customizing CometD Configuration

var cometd = require('cometd-nodejs-server');
var cometdServer = cometd.createCometDServer({
    logLevel: 'debug', // Emits logging on the console
    timeout: 10000, // Heartbeat timeout in milliseconds
    maxInterval: 15000, // Server-side session expiration in milliseconds
    ...
});

Server timeout and CometD timeout

CometD clients send periodic heartbeat messages on the /meta/connect channel. The CometD server holds these heartbeat messages for at most the timeout value (see above), by default 30 seconds.

The NodeJS server also has a timeout property that controls the maximum time to handle a request/response cycle, by default 120 seconds.

You want to be sure that NodeJS' Server.timeout is greater than CometD's CometDServer.options.timeout, especially if you plan to increase the CometD timeout.

Creating Channels and Receiving Messages

var channel = cometdServer.createServerChannel('/service/chat');
channel.addListener('message', function(session, channel, message, callback) {
    // Your message handling here.

    // Invoke the callback to signal that handling is complete.
    callback();
});

Publishing Messages on a Channel

var channel = cometdServer.createServerChannel('/chat');
channel.publish(session, message.data);

Installing a Security Policy

cometdServer.policy = {
    canHandshake: function(session, message, callback) {
        // Your handshake policy here.
        var allowed = ...;
        
        // Invoke the callback to signal the policy result. 
        callback(null, allowed);
    }
};

Sending a Direct Message to a Session

var session = cometdServer.getServerSession(sessionId);
session.deliver(null, '/service/chat', {
    text: 'lorem ipsum'
});

Reacting to Session Timeout/Disconnection

session.addListener('removed', function(session, timeout) {
    if (timeout) {
        // Session was expired by the server.
    } else {
        // Session was explicitly disconnected.
    }
});

Accessing Contextual Information

In certain cases it is necessary to access contextual information such as the HTTP request that carries incoming CometD messages, or the HTTP response that carries outgoing CometD messages.

var channel = cometdServer.createServerChannel('/chat');
channel.addListener('message', function(session, channel, message, callback) {
    // Access contextual information.
    var request = cometdServer.context.request;
    if (request) {
        // You can read headers from the NodeJS HTTP request.
        var myHeader = request.headers['X-My-Header'];
        ...
    }

    var response = cometdServer.context.response;
    if (response) {
        // You can add headers to the NodeJS HTTP response.
        response.setHeader('X-My-Header', 'foo_bar');
        ...
    }

    // Invoke the callback to signal that handling is complete.
    callback();
});

NOTE: always check if the request and response objects are defined; they may not be defined if the transport used is not HTTP but, for example, WebSocket.