Wellington Soares welll

HTTP Streaming (or Chunked vs Store & Forward)

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

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

React "Hello World" Examples

Below are a small collection of React examples to get anyone started using React. They progress from simpler to more complex/full featured.

They will hopefully get you over the initial learning curve of the hard parts of React (JSX, props vs. state, lifecycle events, etc).

Usage

You will want to create an index.html file and copy/paste the contents of 1-base.html and then create a scripts.js file and copy/paste the contents of one of the examples into it.

Limpando os branches que você já fez merge

Olá!

Bem, muitas vezes no dia-a-dia com o git, você abre um branch para a feature, termina, faz merge na master e pronto! Está entregue. O problema é que com isso, seu git fica cheio de branches que são, digamos: INÚTEIS. E claro que com o tempo esses branches se reproduzem como coelhos.

Como fazer para apagar todos esses branches? Você deve ter percebido que apenas um git branch -D meu-branch só apaga o branch no seu computador, e em nenhum remote.

Fácil, é só fazer o código git push origin :meu-branch, que além de ser nem um pouco claro (WTF?), te obriga a fazer isso um a um. Se forem muitos branches, babau!

	#!/bin/bash -e
	# Make sure you have installed ImageMagick
	# http://cactuslab.com/imagemagick/

	# Ensure we're running in location of script.
	cd "`dirname $0`"

	for f in *; do
	if [[ $f == @3x ]];
	then

	// Promise.all is good for executing many promises at once
	Promise.all([
	promise1,
	promise2
	]);

	// Promise.resolve is good for wrapping synchronous code
	Promise.resolve().then(function () {
	if (somethingIsNotRight()) {
	throw new Error("I will be rejected asynchronously!");

	Jenkins Best Practices
	https://en.wikipedia.org/wiki/Continuous_integration<- Read this!
	https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+Best+Practices
	http://www.slideshare.net/andrewbayer/7-habits-of-highly-effective-jenkins-users
	Set up version control of job configurations
	Keep jobs simple! Don't put a ton of bash in each job. If a job needs to do something complex, put it in a script in GitHub and check it out as needed.
	Use templated builders to simplify common tasks
	Keep all scripts in version control - avoid running scripts that live on the Jenkins server filesystem
	Don't install unnecessary plugins - plugins are often written by third parties and can interact with each other in strange ways
	Use LDAP authentication if possible for traceability - avoid anonymous access

	'use strict';

	var React = require('react');

	var BzIframe = React.createClass({

	propTypes: {
	src: React.PropTypes.string.isRequired,
	onLoad: React.PropTypes.func
	},

	void Foo( int * ptr,
	int const * ptrToConst,
	int * const constPtr,
	int const * const constPtrToConst )
	{
	*ptr = 0; // OK: modifies the "pointee" data
	ptr = NULL; // OK: modifies the pointer

	*ptrToConst = 0; // Error! Cannot modify the "pointee" data
	ptrToConst = NULL; // OK: modifies the pointer

	Slides -https://slides.com/chandrikagole/workshop-slides
	CoffeeShop app repo - https://github.com/strongloop/loopback-example-coffee-shop
	Statsd url - $ slc run --metrics statsd://ec2-54-203-118-202.us-west-2.compute.amazonaws.com:8125
	pm-server - http://ec2-54-244-141-80.us-west-2.compute.amazonaws.com:7777
	coffeeshop.json - https://raw.githubusercontent.com/strongloop/loopback-example-coffee-shop/master/coffeeshops.json
	coffee-shop.js - https://raw.githubusercontent.com/strongloop/loopback-example-coffee-shop/master/common/models/coffee-shop.js
	index.html - https://raw.githubusercontent.com/strongloop/loopback-example-coffee-shop/master/client/index.html
	coffee.js - https://raw.githubusercontent.com/strongloop/loopback-example-coffee-shop/master/common/models/coffee.js
	loadtest.js - https://raw.githubusercontent.com/strongloop/loopback-example-coffee-shop/master/loadtest.js