Santi Herrero santihbc

## gist:5289098
./configure  \
--prefix=/usr  \
--mandir=/usr/share/man  \
--infodir=/usr/share/info  \
--sysconfdir=/private/etc  \
--with-apxs2=/usr/sbin/apxs  \
--enable-cli  \
--with-config-file-path=/etc  \
--with-libxml-dir=/usr  \
--with-openssl=/usr  \

## twitter_streaming.js
var util = require('util'),
    http = require('http'),
    events = require('events');

var Twitter = function(opts) {
    this.username = opts.username;
    this.password = opts.password;
    this.track = opts.track;
    this.data = '';
};

## index.html
<!DOCTYPE html>
<html>
	<head>
		<meta http-equiv="Content-Type" content="text/html;charset=utf-8">
		<title>Chronological Diagram of Asia</title>
		<script type="text/javascript" src="http://mbostock.github.com/d3/d3.v2.js"></script>
		<style type="text/css">
		.chart {
			shape-rendering: crispEdges;
		}

## meteor-async.md

      
              1 file
            
          
              0 forks
            
          
                0 comments
              
            
              0 stars
            
          
                santihbc
                / meteor-async.md
            
            
              Created
              June 18, 2013 05:57
                — forked from possibilities/meteor-async.md
            
          
    From Meteor's documentation:

In Meteor, your server code runs in a single thread per request, not in the asynchronous callback style typical of Node. We find the linear execution model a better fit for the typical server code in a Meteor application.

This guide serves as a mini-tour of tools, trix and patterns that can be used to run async code in Meteor.
Basic async

Sometimes we need to run async code in Meteor.methods. For this we create a Future to block until the async code has finished. This pattern can be seen all over Meteor's own codebase:

  
## domains.md

      
              1 file
            
          
              0 forks
            
          
                0 comments
              
            
              0 stars
            
          
                santihbc
                / domains.md
            
            
              Created
              July 2, 2013 08:26
            
          
    Node Error Handling and Domains

"Occurrences in this domain are beyond the reach of exact prediction because of the variety of factors in operation, not because of any lack of order in nature." - Albert Einstein

"Master of my domain" - Larry David

Error handling in an asynchronous language works in a unique way and presents many challenges, some unexpected. This tutorial reviews the various error handling patterns available in node, and explains how domains can be used to improve it.
There are four main error handling patterns in node:

Error return value


## .gitconfig
#
# Working with branches
#

# Get the current branch name (not so useful in itself, but used in
# other aliases)
branch-name = "!git rev-parse --abbrev-ref HEAD"
# Push the current branch to the remote "origin", and set it to track
# the upstream branch
publish = "!git push -u origin $(git branch-name)"

## backboneconf2013
code delimiters: <% %>

# keynote
    - your business logic will live longer than your interface
    - stateless
        - no "spaghetti state"
        - application should be able to reflect any combination of data
        - views should transparently reflect models
    - backbone patterns
        - custom model methods

## backboneconf2013
code delimiters: <% %>

# keynote
    - your business logic will live longer than your interface
    - stateless
        - no "spaghetti state"
        - application should be able to reflect any combination of data
        - views should transparently reflect models
    - backbone patterns
        - custom model methods

## ohmyzsh pluguin
#================================#
#       Folder shortcuts         #
#================================#
alias home='cd ~'
alias desktop='cd ~/Desktop'
alias downloads='cd ~/Downloads'
alias edpuzzle= 'cd ~/Sites/edpuzzle/edpuzzle'

# Projects
sites() { cd ~/Sites/$1; }

## JasmineSpec.coffee
describe 'App.HeaderModule', ->

  beforeEach ->
    @headerModule = window.App.HeaderModule

  it 'should exist', ->
    expect(@headerModule).not.toBeUndefined()

  describe 'starting', ->
	./configure \
	--prefix=/usr \
	--mandir=/usr/share/man \
	--infodir=/usr/share/info \
	--sysconfdir=/private/etc \
	--with-apxs2=/usr/sbin/apxs \
	--enable-cli \
	--with-config-file-path=/etc \
	--with-libxml-dir=/usr \
	--with-openssl=/usr \
	var util = require('util'),
	http = require('http'),
	events = require('events');

	var Twitter = function(opts) {
	this.username = opts.username;
	this.password = opts.password;
	this.track = opts.track;
	this.data = '';
	};
	<!DOCTYPE html>
	<html>
	<head>
	<meta http-equiv="Content-Type" content="text/html;charset=utf-8">
	<title>Chronological Diagram of Asia</title>
	<script type="text/javascript" src="http://mbostock.github.com/d3/d3.v2.js"></script>
	<style type="text/css">
	.chart {
	shape-rendering: crispEdges;
	}
	#
	# Working with branches
	#

	# Get the current branch name (not so useful in itself, but used in
	# other aliases)
	branch-name = "!git rev-parse --abbrev-ref HEAD"
	# Push the current branch to the remote "origin", and set it to track
	# the upstream branch
	publish = "!git push -u origin $(git branch-name)"
	code delimiters: <% %>

	# keynote
	- your business logic will live longer than your interface
	- stateless
	- no "spaghetti state"
	- application should be able to reflect any combination of data
	- views should transparently reflect models
	- backbone patterns
	- custom model methods
	#================================#
	# Folder shortcuts #
	#================================#
	alias home='cd ~'
	alias desktop='cd ~/Desktop'
	alias downloads='cd ~/Downloads'
	alias edpuzzle= 'cd ~/Sites/edpuzzle/edpuzzle'

	# Projects
	sites() { cd ~/Sites/$1; }
	describe 'App.HeaderModule', ->

	beforeEach ->
	@headerModule = window.App.HeaderModule

	it 'should exist', ->
	expect(@headerModule).not.toBeUndefined()

	describe 'starting', ->