- to solve some problems hopefully
- developing a shared understanding
I hereby claim:
To claim this, I am signing this object:
The standard way of understanding the HTTP protocol is via the request reply pattern. Each HTTP transaction consists of a finitely bounded HTTP request and a finitely bounded HTTP response.
However it's also possible for both parts of an HTTP 1.1 transaction to stream their possibly infinitely bounded data. The advantages is that the sender can send data that is beyond the sender's memory limit, and the receiver can act on
#!/usr/bin/env bash | |
set -o pipefail | |
slow_compute_hash() { | |
find "$1" -type f -exec md5sum {} \; | sort -k 2 | md5sum | |
} | |
fast_compute_hash() { | |
find "$1" -type f -print0 | sort -z | xargs -0 md5sum | md5sum | |
} |
(function (global, factory) { | |
typeof exports === 'object' && typeof module !== 'undefined' ? module.exports = factory() : | |
typeof define === 'function' && define.amd ? define(factory) : | |
(global.mixpanel = factory()); | |
}(this, function () { 'use strict'; | |
var Config = { | |
DEBUG: false, | |
LIB_VERSION: '2.22.4' | |
}; |
;; -*- geiser-scheme-implementation: 'mit -*- | |
(load "sdf/manager/load") | |
(manage 'new-environment 'combinators) | |
#!/bin/bash | |
# | |
# DESCRIPTION | |
# utility to aid in the setup of temporary AWS assumed role credentials | |
# | |
# USAGE | |
# pipe the output of aws sts assume-role to this script and redirect the output | |
# to append the temporary credentials to your $HOME/.aws/credentials | |
# | |
# you may supply a profile name as an argument. if you do not, then one is generated |
#!/usr/bin/env bash | |
set -eo pipefail | |
if [[ "$#" -eq 0 ]]; then | |
cat <<EOF | |
usage: $(basename $0) <REGION> [OPTIONS] | |
REGION - a valid AWS region e.g. us-east-1 | |
OPTIONS - any valid AWS CLI options e.g. --profile home | |
EOF |