subfuzion

Common Options

-#, --progress-bar Make curl display a simple progress bar instead of the more informational standard meter.

-b, --cookie <name=data> Supply cookie with request. If no =, then specifies the cookie file to use (see -c).

-c, --cookie-jar <file name> File to save response cookies to.

rhossi

var aws = require('aws-sdk'),
    fs = require('fs'),
    crypt = require("crypto");

function getMD5HashFromFile(file){
    var hash = crypt.createHash("md5")
        .update(file)
        .digest("base64");
    return hash;
}

mkusher

var gulp = require("gulp");
var browserify = require("browserify");
var babelify = require("babelify");
var source = require("vinyl-source-stream");
var config = {
    src: "index.js",
    filename: "bundle.js",
    dest: "./"
};
var extensions = ['.js', '.ts', '.json'];

joyrexus

Nice answer on stackoverflow to the question of when to use one or the other content-types for POSTing data, viz. application/x-www-form-urlencoded and multipart/form-data.

“The moral of the story is, if you have binary (non-alphanumeric) data (or a significantly sized payload) to transmit, use multipart/form-data. Otherwise, use application/x-www-form-urlencoded.”

---

Matt Bridges' answer in full:

The MIME types you mention are the two Content-Type headers for HTTP POST requests that user-agents (browsers) must support. The purpose of both of those types of requests is to send a list of name/value pairs to the server. Depending on the type and amount of data being transmitted, one of the methods will be more efficient than the other. To understand why, you have to look at what each is doing

ijy

<!--
    ALTERNATIVE SEARCH & REPLACE
    string:     The text to be evaluated
    replace:    The character or string to look for in the above string
    with:       What to replace it with

    Slightly more long winded approach if that's how you prefer to roll.
--> 

<xsl:template name="string-replace">

benmj

/*
I'm converting an existing web-app to angular. We made extensive use of the
Google Visualization library in the past. It's a powerful, although
complicated API, so I was anxious to get it wrapped up in angular. This
populates a table with data returned from a custome service 'Account'
*/

'use strict';

/* Directives */