domenic

public class A
{
    private Bable b;
    private Cable c;
    
    public A(Bable b, Cable c)
    {
        this.b = b;
        this.c = c;
    }

domenic

// `promise` is some operation that may succeed (fulfill) or fail (reject)
var newPromise = promise.then(
    function () {
        return delay(1000);
    },
    writeError
);

// If `promise` fulfills, `newPromise` will fulfill in 1000 ms.
// If `promise` rejects and writing to the error log succeeds,

domenic

describe("when grant_type is password", function () {
    describe("and client_id/client_secret from Authorization header are valid", function () {
        describe("and username/password pass user authentication", function () {
            it("should grant an access token in the appropriate response format", function (done) {

        describe("and username/password do not pass user authentication", function () {
            itShouldRejectWith(restify.UnauthorizedError, "invalid_client");

        describe("and the user authentication process fails in an unexpected way", function () {
            it("should pass that error through", function (done) {

domenic

"use strict";

// Uses jQuery and Q.

var API_KEY = "whatever";

function getFlickrResponseAsync(method, responseProperty, params) {
    var deferred = Q.defer();

    $.ajax("http://www.flickr.com/services/rest/", {

domenic

var mongoose = require('mongoose');
mongoose.connect('mongo://localhost/test');
var conn = mongoose.connection;

var users = conn.collection('users');
var channels = conn.collection('channels');
var articles = conn.collection('articles');

var insertUsers = Q.nfbind(users.insert.bind(users));
var insertChannels = Q.nfbind(channels.insert.bind(channels));

domenic

Using Static Helpers

There are some basic patterns for creating promises that are so common, you will want to use Q's static helpers for them. The most important of these are Q.resolve and Q.reject.

Use Q.resolve to create either a fulfilled promise, if you pass a fulfillment value directly, or to simply subsume another promise. That is, in general,

domenic

var LICENSE_TYPE = Object.freeze({
    UNRESTRICTED: 0,
    BASIC: 1,
    ENHANCED: 2,
    SOCIAL: 3,
    FREE_TRIAL: 4
});

productTranslations.unrestrictedLicenseFormatCodes = ["EE", "EF", "EG", "EY", "E9", "D8", "DX"];
productTranslations.socialLicenseFormatCodes = ["EP", "EH", "DU", "DW"];

domenic

Node.js core does its best to treat every platform equally. Even if most Node developers use OS X day to day, some use Windows, and most everyone deploys to Linux or Solaris. So it's important to keep your code portable between platforms, whether you're writing a library or an application.

Predictably, most cross-platform issues come from Windows. Things just work differently there! But if you're careful, and follow some simple best practices, your code can run just as well on Windows systems.

Paths and URLs

On Windows, paths are constructed with backslashes instead of forward slashes. So if you do your directory manipulation

domenic

Comparing Different Implementations of process.nextTick using the Q test suite.

Used: q-spec.js@a1a416.

Implementations compared:

Based on MessageChannel

This is currently in Q:

domenic

Opening Remarks

• Fun feature of the JS language that few know about, and even fewer use.
• It's in "ECMAScript 5" (explain this).
• Browser support: IE9 or above. Plus MOBILE!!

Series of Demos

Getters