Standard practices say no non-root process gets to talk to the Internet on a port less than 1024. How, then, could I get Node talking on port 80 on EC2? (I wanted it to go as fast as possible and use the smallest possible share of my teeny tiny little micro-instance's resources, so proxying through nginx or Apache seemed suboptimal.)
Alter the port the script talks to from 8000 to 80:
}).listen(80);
| angular.module('myApp').directive('addthisToolbox', ['$timeout', function($timeout) { | |
| return { | |
| restrict : 'A', | |
| transclude : true, | |
| replace : true, | |
| template : '<div ng-transclude></div>', | |
| link : function($scope, element, attrs) { | |
| $timeout(function () { | |
| addthis.init(); | |
| addthis.toolbox($(element).get(), {}, { |
Heil PR40 Package - http://www.bswusa.com/Dynamic-Microphones-Heil-Sound-PR40-Package-P7628.aspx
This is a great deal, and is a perfect mic for this stuff.
OC White Boom - http://www.ocwhite.com/broadcast-arms/proboomtm-elite-extended-reach-mic-arm-with-riser-45-reach-12-vertical-riser.html
The kit comes with a boom. It is decent, I guess, but this OC White boom is badass prostyle with a 4' reach and a 15" riser that lets it live behind my monitor.
All of the below properties or methods, when requested/called in JavaScript, will trigger the browser to synchronously calculate the style and layout*. This is also called reflow or layout thrashing, and is common performance bottleneck.
Generally, all APIs that synchronously provide layout metrics will trigger forced reflow / layout. Read on for additional cases and details.
elem.offsetLeft, elem.offsetTop, elem.offsetWidth, elem.offsetHeight, elem.offsetParent