Skip to content

Instantly share code, notes, and snippets.

View Qijiang60's full-sized avatar

Qi Jiang Qijiang60

6 followers · 21 following
  • Nanchang, Jiangxi
View GitHub Profile
@Qijiang60
Qijiang60 / curl.md
Created November 10, 2016 15:17 — forked from btoone/curl.md
A curl tutorial using GitHub's API

Introduction

An introduction to curl using GitHub's API

The Basics

Makes a basic GET request to the specifed URI

curl https://api.github.com/users/caspyin
@Qijiang60
Qijiang60 / github_oauth_busy_developer_guide.md
Created November 10, 2016 15:07 — forked from technoweenie/github_oauth_busy_developer_guide.md
GitHub OAuth Busy Developer's Guide

GitHub OAuth Busy Developer's Guide

This is a quick guide to OAuth2 support in GitHub for developers. This is still experimental and could change at any moment. This Gist will serve as a living document until it becomes finalized at Develop.GitHub.com.

OAuth2 is a protocol that lets external apps request authorization to private details in your GitHub account without getting your password. All developers need to register their application before getting started.

Web Application Flow

  • Redirect to this link to request GitHub access:
@Qijiang60
Qijiang60 / Design Patterns: Adapter vs Facade vs Bridge.md
Created October 28, 2016 12:36 — forked from Integralist/Design Patterns: Adapter vs Facade vs Bridge.md
Design Patterns: Adapter vs Facade vs Bridge

The three design patterns (Adapter, Facade and Bridge) all produce the result of a clean public API. The difference between the patterns are usually due to a subtle context shift (and in some cases, a behavioural requirement).

Adapter

The primary function of an Adapter is to produce a unified interface for a number of underlying and unrelated objects.

You will notice this pattern being utilised in many applications. For example, ActiveRecord (the popular Ruby ORM; object-relational mapping) creates a unified interface as part of its API but the code underneath the interface is able to communicate with many different types of databases. Allowing the consumer of the API to not have to worry about specific database implementation details.

The principle structure of this pattern is: