Introduces 'connect' event on both client (http.ClientRequest) and
server (http.Server).

Refs: #2259, #2474.
Fixes #1576.

This is necessary to use SSL over HTTP tunnels.

Refs #2259, #2474.
Fixes #2489.

This makes API even with tls.connect().
Refs #1983.

See also:
http://groups.google.com/group/nodejs-dev/msg/3b6dbcc4a9a82d99

Fixes #2487.

Refs #1983.

Refs #1983.

Refs #1983.

Previous API used form:

    tls.connect(443, "google.com", options, ...)

now it's replaced with:

    tls.connect({port: 443, host: "google.com", ...}, ...)

It simplifies argument parsing in `tls.connect` and makes the API
consistent with other parts.

Fixes #1983.

Passing an options object with {thread:true} to .fork() or .spawn() will run the
target script in a thread instead of a separate process.

No longer necessary, each isolate now waits until its subordinate isolates have
exited.

Parent and child isolates can now pass arbitrary binary messages between each
other. The messages are sent and received through a thread-safe queue that
wakes up the event loop of the receiving thread.

- create a typed array from a node::Buffer object
- update TypedArray::set() to spec
- add TypedArray::get() method

Fixes symbol lookup errors when loading an addon module on Linux.

fixes #2465

Fixes #2388

Conflicts:
	src/udp_wrap.cc

SecureContext.setOptions() is backed by SSL_CTX_set_options() which, contrary to
what the name suggests, is additive: it doesn't set options, it adds them to the
already active options.

Hence the need for SecureContext.clearOptions(), which lets you unset active
options.

Creating a file event watcher with fs.watch({persistent:false}) should not block
the event loop.

Copies the POST request data verbatim into the response body.

Unfortunately valgrind must be used to see the bad read. It would be nice if
we could improve this test to cause a segfault.

Conflicts:
	src/platform_win32.cc