gbL-jsMop v0.14.4

gbL.jsMop

Sunday, 10 June 2010
Version 0.9.3
N.B. Much of the code below has not been tested. For tested examples, see the tests and scenarios included. Feel free to contact me with abuse or questions: disqus at http://goofballLogic.github.com/gbL.jsMop

Preamble

This is a library for message passing in javascript. The "mop" in jsMop is an acronym referring to OOP, but "message-oriented" instead of "object-oriented". A central "mop" object is used to send and receive messages (in place of a native message exchange construct).

http://www.purl.org/stefan_ram/pub/doc_kay_oop_en

Environment

Designed to work specifically in the browser, or in Node, but should work in most CommonJS environments.

Running/Building tests

####Without a browser (mocha) You will need to

npm install mocha
npm install expect.js

and then

make test

####In the browser Just browse to

test-browser/browserTests.html

####Building (and opening) the browser tests You will need to

npm install browserify

and then

make browser-test

Examples

Example usage can be found in the /test/scenarios folder.

Basic usage

####First step is to spin up a hub for the messages:

var mop = new gbL.jsMop.Mop();

or

var mop = new require("gbL.jsMop").Mop();

####Sending

Then, to send a message:

mop.send("Hello world").as("test");

which sends a message with subject test and payload of Hello world.

####Receiving If I am an object wanting to receive this sort of message, I would include a method named receive_test:

var receiver = {
    receive_test: function(data) {
        console.log(data);
    }
};

and I would register with the hub to receive messages:

mop.register(receiver, "My first receiver");

#####or

if I don't wish to register as an object, I can regsiter a call back function:

mop.registerHandler("test", function(data) {
    console.log(data);
});

##Debugging There are a few tools to help with debugging message passing. For analysis of registered objects and handlers, just send a census message:

var registered = mop.send().as("census");
console.log("Registered receivers: " + registered.join(", ");

You may also wish to turn on console logging by using:

mop.debug = true;

or

mop.send.debug = true;

##Bootstrapping modules Say you have a set of modules which contain objects wishing to participate in message exchange through a given mop.

For example, in Node, you might have a console-logger.js:

(function(context) {
	
	var mop;
	
	context.bootstrap = {
		init: function(initMop) {
			mop = initMop;
			initMop.Register(loggingSingleton, "Console logger");
		}
	}
	
	var loggingSingleton = new function() {
		return {
			receive_log: function(data) {
				var label = mop.topics.slice(1).join(" ");
				console.log(label, data);
			}
		};
	}();
	
})(module.exports);

and then as part of bootstrapping, include the console-logger:

var mop = new require("gbL.jsMop").Mop();
mop.boot({
	"logger": require("console-logger"),
	"worker": require("important-worker-module"),
	"another": require("another-important-worker-module")
});

which will mean that e.g. the following will print my friend's name to the console:

mop.send("Lisa Jue Bishop").as("log the name of my dear friend");

#####Or In the browser, you might have a ticker object:

(function(context) {
	var mop;
	
	context.Ticker = {
		bootstrap: {
			init: function(jsMop) {
				mop = jsMop;
				mop.register(new Ticker(), "Ticker");
			}
		}
	};
	
	function Ticker() {
		// private state and behaviours
		var cancelled = false;
		function tick() {
			mop.send().as("tick");
			if(!cancelled) setTimeout(100, tick);
		}
		// message receivers
		return {
			receive_cancel_ticker: function() {
				cancelled = true;
			}
		}
	}
	
})(gbL.Stocks || { gbL.Stocks = {} });

which you could then boot as so:

var mop = new gbL.jsMop.Mop();
mop.boot({
	"ticker": gbL.Stocks.Ticker,
	"symbol-list": gbL.Stocks.SymbolLister
});

which will cause tick messages to be sent until:

mop.send().as("cancel ticker");

is sent.

##Further patterns

####Partial subject match If you want to accept messages about a more general subject than those specified for the messages, you can receive messages which match the start of the subject:

function HelloListener() {
	this.receive_hello = function() {
		console.log(mop.subject);
	};
}

would receive:

mop.send().as("hello world");

but would also receive:

mop.send().as("hello heaven");
mop.send().as("hello hell");

####Filtering messages If you want to filter the messages received for a given subject, you can attaching a filtering function, like so:

function BeerWatcher() {
	this.receive_important_notification = function(notification) {
		console.log("CRITICAL: " + notification);
	};
	this.receive_important_notification.filter = function(topics, data)
	{
		// only interested in notifications mentioning beer in their subject
		return ~topics.join(" ").indexOf("beer");
	};
}

####Filtering lots of handlers If you have an object which only wants to receive messages which mention a specific ID, you can:

function CalculationNode(nodeId, calculationStrategy) {
	// private state and behaviour
	var parameters, lastResult;
	function reset(preserveResult) { 
		parameters = [];
		preserveResult || lastResult = null; 
	}
	function execute() {
		return (lastResult = calculationStrategy.apply(this, parameters));
	}
	reset();
	
	// message receivers
	this.receive_reset_parameters = function() {
		reset(true);
	};
	this.receive_parameterise = function() {
		for(var i in arguments) parameters.push(arguments[i]);
	};
	this.receive_calculate = function() {
		mop.send(execute()).as("result for node " + nodeId);
	};

	mop.setReceiveFilters(this, function(topics, data) {
		// all the above, only for messages about this node (by Id)
		return ~topics.indexOf("node " + nodeId);
	});
	
	// unfiltered receivers
	this.receive_global_reset = function() {
		reset();
	};
	this.receive_return_results = function() {
		return new function() { this[nodeId] = lastResult; };
	}
}

####Adapter You may wish to use an adapter to send and receive messages, especially when you want to mix the message-passing paradigm with calling methods directly. For example, using the revealing module pattern, you might do something like:

function ServiceAgent() {

    var configuration = null;
	var fetched = [];
	
    function saveConfiguration(config) {
        configuration = $(config).clone();
    }
    
	function dataGet(toGet) {
		return mop
			.send(configuration.baseUrl, "orders")
			.as("ajax GET");
	}
	
	function injestData(data) {
		fetched.push(data);
	}
	
    // inner facet (mop adapter)
    mop.register({
    	receive_configuration: saveConfiguration,
    	receive_data_received: injestData,
    }, "Service Agent");
    
	// outer facet (revealed methods)
    return {
        listOrders: function() {
        	var data = null;
        	if(dataGet("orders")) data = fetched.pop();
        	return data;
       	}
    };
}

An object constructed by this function will expect to collaborate with

• An object whose responsibility is to broadcast configuration (sending messages with subject "configuration")
• An object whose responsibility is to make AJAX calls (receiving subjects beginning with "ajax", and sending back the data with subject "data received")

And it exposes a method which can be called directly as so:

var serviceAgent = new ServiceAgent();
var orders = serviceAgent.listOrders();