... or Why Pipelining Is Not That Easy
Golang Concurrency Patterns for brave and smart.
By @kachayev
| // | |
| // API.swift | |
| // | |
| // Created by Taro Minowa on 6/10/14. | |
| // Copyright (c) 2014 Higepon Taro Minowa. All rights reserved. | |
| // | |
| import Foundation | |
| typealias JSONDictionary = Dictionary<String, AnyObject> |
| package main | |
| import ( | |
| "net/http" | |
| "database/sql" | |
| "fmt" | |
| "log" | |
| "os" | |
| ) |
| /* | |
| Purpose: | |
| Convert (or Serialize) an object to a JSON String or Dictionary. | |
| Usage: | |
| Use 'Serialize.toJSON' on instances of classes that: | |
| - Inherit from NSObject | |
| - Implement 'Serializable' protocol | |
| - Implement the property 'jsonProperties' and return an array of strings with names of all the properties to be serialized |
... or Why Pipelining Is Not That Easy
Golang Concurrency Patterns for brave and smart.
By @kachayev
Here's a little walkthrough of how Yannick and I are using feature branches and pull requests to develop new features and adding them to the project. Below are the steps I take when working on a new feature. Hopefully this, along with watching the process on Github, will serve as a starting point to having everyone use a similar workflow.
Questions, comments, and suggestions for improvements welcome!
When starting a new feature, I make sure to start with the latest and greatest codebase:
git checkout master
Here's how I set up a tiny Nginx/Rails server that uses HTTPS via a Let's Encrypt issued certificate.
I use the smallest DigitalOcean droplet (512 MB) here, which is built from the "Ubuntu Ruby on Rails on 14.04" image provided by them.
HTTP/2 has arrived in most recent browsers and is therefore ready to use (http://caniuse.com/#search=http2).
The Let's-Encrypt project allows you to generate SSL certificates for free. To start using it clone letsencrypt from github:
$ git clone https://github.com/letsencrypt/letsencrypt