owenallenaz

<cfcomponent>
	<cfset this.name = "mySpecialApp">
	<cfset this.datasource = "rc_cms">
	<cfset this.ormEnabled = true>
	
	<cffunction name="onError">
		<cfdump var="#arguments#">
	</cffunction>
</cfcomponent>

owenallenaz

component {
	this.name = "testingApp";

	public function onRequestStart() {
		Application.component1 = CreateObject("component1");
		Application.component2 = CreateObject("component2");
		Application.component3 = CreateObject("component3");
	}
}

owenallenaz

component {
	this.name = "testingApp";

	public function onApplicationStart() {
		// counter to prove the cron.cfm is firing
		application.counter = 0;
	}

	public function onRequestEnd() {
		// specify an index for the cache

owenallenaz

var domain = require("domain");
var d = domain.create();

d.on("error", function() {
	console.log("domain caught");
});

try {
	d.run(function() {
		process.nextTick(function() {

owenallenaz

Example showing async.waterfall which functions semantically the same as promises.

<script src="http://cdnjs.cloudflare.com/ajax/libs/async/1.22/async.min.js"></script>

<script>
	// waterfall wrapper to try/catch each method in a waterfall
	var catchWaterfall = function(arr, cb) {
		var calls = [];
		arr.forEach(function(val) {

owenallenaz

foo

foo

foo

owenallenaz

npm: 34ms
json: 7ms
317780 307781

owenallenaz

var async = require("async/");
var mongodb = require("mongodb");
var assert = require("assert");

mongodb.MongoClient.connect("mongodb://127.0.0.1/test", {}, function(err, conn) {
	if (err) { throw err; }
	
	var collection = conn.collection("test");
	
	var newDocs = [];

owenallenaz

In the following test code there are two things to look for.

"in cb 0 0 1" means that it is in the callback after the call to mongodb, and the numbers are "expectedNum actualNum stackSize". The expectedNum and actualNum match, and they do. The stackSize should always be 1. In the event the stackSize is not 1 it means that the domains are not being properly entered and exited. If the stackSize grows domains are leaking.

Another important marker is the "after exit" and "end call" blocks, they should always be undefined. In the event that they are not undefined it means that a domain is lingering after exit, which results in subsequent code being in a domain it shouldn't, as well as a possible memory leak.

From the test file it appears that both setImmediate and process.nextTick() work.

owenallenaz

------------
test { populationSize: 100000000,
  sampleSize: 1000,
  bias: 50,
  marginOfError: 0.030990321069650117 }
inMarginOfError { yes: 940, no: 60 }
predictedElections { wins: 513, ties: 34, losses: 453 }
------------
test { populationSize: 100000000,
  sampleSize: 1000,