removing 'close' listener properly
Merge #660 r=@jiahuang: removing 'close' listener properly
Fix gyp options that were lost in #651. Fixes #663
Merge #664 r=@natevw: Fix gyp options that were lost in #651

Fixes #663
Adding empty domains implementation until we can implement and test it
Merge #667 r=@johnnyman727: Adding empty domains implementation until we can implement and test it

Empty Domain implementation until we can implement and test a legitimate one.
Buffer.fill with strings
Merge #671 r=@johnnyman727: Buffer.fill with strings

Related to #666

This is the Node.js version `0.10.x` implementation of `Buffer.fill`. 

@johnnyman727 we can merge this for now and then when Node.js `0.12.x` is released we'll merge the next one that I'll submit in 5 minutes.
do not destroy free (i.e. intentionally idle) sockets (node 0.11.x "actually useful keep-alive" behavior broken in https://github.com/tessel/runtime/commit/7e42f6fb8402ee50d612f5b889b5192ef68ebf15)
we do not want outgoing message to end socket on its own (close is managed elsewhere, so connection may be reused by keep-alive!)
make sure outbox ends, then unpipe outbox from socket when it does. this gets rid of the EventEmitter leaks on #655, although still seeing one warning during http tests.
Merge #673 r=@jiahuang: Fix http OutgoingMessage leaks, improve connection reuse a bit

This fixes the leaks on https://github.com/tessel/runtime/issues/655 and also fixes up some halfway-related issues noticed in other posthumous 'http' review.

(Note: there's still one outstanding "leak" warning that I see when running http tests under posix, but not with the superficially associated test's isolate code itself. So I suspect this might actually be related to the global 'tcp-close' but even if not can be dealt with separately should it cause real-world problems.)
use the force luke