carsonmcdonald

var tls = require('tls');
var fs = require('fs');
var Buffer = require('buffer').Buffer;
var zlib = require('zlib');
var BufferList = require('bufferlist');
var Binary = require('bufferlist/binary');
var Put = require('put');
var http = require('http');

var options = 

rstacruz

# ## Backbone model caching
# This is a simple solution to the problem "how do I make less requests to
# my server?".
#
# Whenever you need a model instance, this will check first if the same thing
# has been fetched before, and gives you the same instance instead of fetching
# the same data from the server again.
#
# Reusing the same instance also has the great side-effect of making your
# model changeable from one part of your code, with your changes being available

ry

var http = require('http')
var fork = require('child_process').fork;

function fib(n) {
  if (n < 2) {
    return 1;
  } else {
    return fib(n - 2) + fib(n - 1);
  }
}

kevinswiber

{
  "_links": {
    "self": { "href": "/orders" },
    "next": { "href": "/orders?page=2" },
    "find": { "href": "/orders{?id}", "templated": true }
  },
  "_embedded": {
    "orders": [{
        "_links": {
          "self": { "href": "/orders/123" },

piscisaureus

Locate the section for your github remote in the .git/config file. It looks like this:

[remote "origin"]
	fetch = +refs/heads/*:refs/remotes/origin/*
	url = [email protected]:joyent/node.git

Now add the line fetch = +refs/pull/*/head:refs/remotes/origin/pr/* to this section. Obviously, change the github url to match your project's URL. It ends up looking like this:

mikekelly

{
  "_links": {
    "self": { "href": "/foo" },
  },
  "_controls": {
    "attack": {
      "target": "/attacks",
      "method": "POST",
      "headers": {
        "Content-Type": "application/json"

dergachev

OS X Screencast to animated GIF

This gist shows how to create a GIF screencast using only free OS X tools: QuickTime, ffmpeg, and gifsicle.

Instructions

To capture the video (filesize: 19MB), using the free "QuickTime Player" application:

kevinswiber

var pipeworks = require('pipeworks');

var worker1 = pipeworks()
  .fit(function(context, next) {
    console.log('in worker 1');
    next(context);
  });

var worker2 = pipeworks()
  .fit(function(context, next) {

steveklabnik

Versioning is an anti-pattern
=============================

We often say "use the right tool for the job", but when managing change
in software systems, we always use versioning. Hypermedia APIs are
actually hindered by introducing versioning and manage change in a
different way. With that in mind, there are also a lot of options for
managing change in a Hypermedia API. We'd like to change our service and
break as few clients as possible. Versioning is only one way to manage
change, though... and my contention is that it's not appropriate for

kevinswiber

Feature: Root Resource
	As an API client
	I want to see the root resource
	So that I have a starting point to complete my task.

	Scenario: Request the root
    		Given an anonymous client
		When I make a GET request to /
		Then I should get a 200 status code
    		And the content type should be JSON