kevinswiber

RPC vs REST

Here's a brief analysis of RPC vs. REST based on one person's opinion.

• RPC
  • Contracts
  • Benefits
  • Problems
• REST (URL-based)
  • Contracts

arobson

Abstraction Suggestions

Summary: use good/established messaging patterns like Enterprise Integration Patterns. Don't make up your own. Don't expose transport implementation details to your application.

Broker

As much as possible, I prefer to hide Rabbit's implementation details from my application. In .Net we have a Broker abstraction that can communicate through a lot of different transports (rabbit just happens to be our preferred one). The broker allows us to expose a very simple API which is basically:

• publish
• request
• start/stop subscription

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

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

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) {

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:

mikekelly

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

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 = git@github.com: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:

kevinswiber

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

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);
  }
}