domenic

This article has been given a more permanent home on my blog. Also, since it was first written, the development of the Promises/A+ specification has made the original emphasis on Promises/A seem somewhat outdated.

You're Missing the Point of Promises

Promises are a software abstraction that makes working with asynchronous operations much more pleasant. In the most basic definition, your code will move from continuation-passing style:

getTweetsFor("domenic", function (err, results) {
 // the rest of your code goes here.

christiannelson

# References:
#   http://blog.mixu.net/2011/08/13/nginx-websockets-ssl-and-socket-io-deployment/
#   http://blog.exceliance.fr/2012/09/10/how-to-get-ssl-with-haproxy-getting-rid-of-stunnel-stud-nginx-or-pound/
#

global
    nbproc  2
    maxconn 16384

defaults

TooTallNate

var fs = require('fs');
var lame = require('lame');
var Speaker = require('speaker');

fs.createReadStream(process.argv[2])
  .pipe(new lame.Decoder())
  .on('format', function (format) {
    this.pipe(new Speaker(format));
  });

JamieMason

#!/bin/bash

# Functions ==============================================

# return 1 if global command line program installed, else 0
# example
# echo "node: $(program_is_installed node)"
function program_is_installed {
  # set to 1 initially
  local return_=1

mcollina

NetworkButtonJSON

NetworkButtonJSON is a forest of network enabled leds that switch on and off on simultaneosly. Join the forest, build a networked LED.

You should:

• mount an Arduino Ethernet Shield.
• build an Arduino-based prototype with the following schema:

dolphin278

Uses capped collection, tailable cursors and streams.

What's here?

• init.js recreates collection capped collection 'queue' on mongodb.
• writer.js spams queue with new messages
• worker.js processes all messages saved to queue,
• onceWorker.js processes only unprocessed messages, so you can spawn several of them and each of your messages will be processed by only one worker.

Steps

makotot

module.exports = function (grunt) {
    'use strict';
	
	// grunt-contrib-watchのlivereloadオプションでlivereload
	grunt.initConfig({

		watch: {
			html: {
				files: '**/*.html',
				tasks: [],

ryanhanwu

var http = require('http'),
    _ = require('underscore'),
    httpProxy = require('http-proxy');
var proxyOptions = {
  router: {
    "api.testAppX.com"     : 'localhost:2041',
    "dev.api.testAppX.com" : 'localhost:2042',
    "www.testAppY.com"     : 'localhost:10520',
    "test.oldApps.com"     : 'localhost:10520',
    'bc.ryanwu.co'         : 'localhost:8888'

jedi4ever

Clustering: The basics

The trick? pass the file descriptor from a parent process and have the server.listen reuse that descriptor. So multiprocess in their own memory space (but with ENV shared usually)

It does not balance, it leaves it to the kernel.

In the last nodejs > 0.8 there is a cluster module (functional although marked experimental)

• http://nodejs.org/api/cluster.html
• Simple cluster example:

benmj

/*global angular: true, google: true, _ : true */

'use strict';

angular.module('geocoder', ['ngStorage']).factory('Geocoder', function ($localStorage, $q, $timeout) {
  var locations = $localStorage.locations ? JSON.parse($localStorage.locations) : {};

  var queue = [];

  // Amount of time (in milliseconds) to pause between each trip to the