Implemented a new property for writable file streams that keeps track
of the bytes written (not queued). This helps when you are piping
another stream to a file, and would like to know how big the file is
without having to issue another stat call.

closes #930

fixes #873

fixes #873

Also, secureOptions flag was added (and passed through) and allows
the context to have all supported SSL_OP_* set via createCredentials.
All SSL_OP_ flags (outside of ALL) have been added to constants.

Conflicts:
	src/platform_sunos.cc
	test/simple/test-os.js

The secureProtocol option to building the SSL context was not being properly
passed through in the credentials in the tls code. This is fixed.

Cherry-pick fail. Breaks linux. Will land again shortly.

This reverts commit e8cf98c8.
This reverts commit d953856d.
This reverts commit 752bbd6b.

https://groups.google.com/d/topic/nodejs-dev/Asr87_YFSkg/discussion

closes #916.

Problem: Sometimes it is useful to read a file from a certain position
to it's end. The current implementation was already perfectly capable
of this, but decided to throw an error when the user tried to omit
the end option. The only way to do this, was to pass {end: Infinity}.

Solution: Automatically assume {end: Infinity} when omitted, and remove
the previous exception thrown. Also updated the docs.

closes #801.

Fixes GH-913.

Signed-off-by: Nick Campbell <nicholas.j.campbell@gmail.com>

Fixes the circular reference problem. Closes GH-822.

Fixes GH-907.

Closes GH-867.

This patch adds support for calling EventEmitter#removeAllListeners
with no parameters in order to remove all listeners as once.

See discussion: https://groups.google.com/forum/#!topic/nodejs-dev/Mcyal1ThTHY

Closes GH-889.

Thanks Frederic. Closes GH-859.

Closes GH-852.

* Always use `this.context` or `self.context`.
* Move `resetContext` to `REPLServer.createContext`.
* Add `REPLServer.resetContext`, memoize `context` here.
* Memoize `exports.repl` in `start`.

Closes GH-851.

Conflicts:
	src/node_version.h
	test/simple/test-buffer.js

However, this test is failing for some quite unrelated issue.
Getting some odd "socket hangup" crashes, and only the first request
ever makes it to the server.