Mitchell Porter mitchellporter

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

###Creating a REST API using Node.js, Express, and MongoDB

####Installing Node.js

Go to http://nodejs.org, and click the Install button. Run the installer that you just downloaded. When the installer completes, a message indicates that Node was installed at /usr/local/bin/node and npm was installed at /usr/local/bin/npm. At this point node.js is ready to use. Let’s implement the webserver application from the nodejs.org home page. We will use it as a starting point for our project: a RESTful API to access data (retrieve, create, update, delete) in a wine cellar database.

Create a folder named nodecellar anywhere on your file system. In the wincellar folder, create a file named server.js.


	import Foundation

	typealias ResponseParserBlock = (ResponseParser) -> Void

	class ResponseParser {

	// MARK: Response information
	private(set) var response: NSHTTPURLResponse?
	private(set) var data: NSData?

	/**
	`ZebraPrinterStatus` is a list of status responses we handle from the printer or during a connection attempt with the printer.
	*/
	enum ZebraPrinterStatus {
	case Ready
	case NotReady([ZebraPrinterError])
	case Unknown

	func message() -> String {
	switch self {

	- (void) audioPCMFrameWasCaptured:(nonnull const AudioStreamBasicDescription )pcmASBD bufferList:(nonnull const AudioBufferList )bufferList time:(CMTime)time sampleRate:(Float64)sampleRate {

	int16_t *fdata = bufferList->mBuffers[0].mData;



	for (int i = 0; i < bufferList->mBuffers[0].mDataByteSize/sizeof(*fdata); i++) {

	fdata = (int16_t)(fdata * 0.1);

	// #!Swift-1.1
	import Foundation


	// MARK: - (1) classes

	// Solution 1:
	// - Use classes instead of struct
	// Issue: Violate the concept of moving model to the value layer
	// http://realm.io/news/andy-matuschak-controlling-complexity/

	//
	// In this custom layer, changes to a "highlightedPercentage" key will switch between showing normal and highlighted image views.
	// In addition, the size of the layer itself changes depending on these image views as well. This layer needs to fully support atomic,
	// model changes to this property as well as animated changes to this key without forcing main thread-bound view layout calls on
	// every frame of animated changes.
	//

	//
	// CATransaction.begin()
	// CATransaction.setDisableActions(true)

	UIView.animateWithDuration(1.0) {
	// Option 1: Animate the player layer
	playerLayer.frame = toViewController.view.bounds

	// Option 2: playerLayer is a sublayer of the container view
	containerView.frame = toViewController.view.bounds
	}

	source 'https://github.com/CocoaPods/Specs.git'
	use_frameworks!
	link_with 'APP_NAME_GOES_HERE'
	platform :ios, '8.0'
	inhibit_all_warnings! # These are all tweaks that were required once all of the Swift issues starting popping up

	target 'APP_NAME_GOES_HERE' do
	pod 'Parse'
	pod 'KGHitTestingViews'
	pod 'Device'

	// View controller is a subclass of GLKViewController

	- (void)viewDidLoad
	{
	[super viewDidLoad];

	self.eaglContext = [[EAGLContext alloc] initWithAPI:kEAGLRenderingAPIOpenGLES2];

	self.ciContext = [CIContext
	contextWithEAGLContext:self.eaglContext