No deprecation messages. Not sure how...

This is to make sure this doesn't break after implementing the new
truly sync require() function.

This patch makes sure nested modules are available in their parents
cache. The module simplification broke this behavior.

See:

http://groups.google.com/group/nodejs/browse_thread/thread/e875132469547d2
http://github.com/ry/node/commit/b73f61a137841cebac8459203b6be3baa1756980

(Going out of the way to be sync)

It now takes an optional showHidden argument that shows hidden/non-enumerable properties of objects.

Also cleanup the lib/sys.js file a bit.

1. Support streaming in the simple case.  Put huge warnings around the
buffering API.
2. Support nested multipart messages.
3. Support various kinds of multipart messages, including all the various
absurdities of multipart email messages.
4. Error out on various invalid types of data that might come through.
5. Gracefully several edge cases that occur when the chunk size is smaller
than the boundary length, or cuts into the \r\n, etc.
6. Provide both positive and negative tests.

http://github.com/ry/node/issues#issue/53

These are actually passed as Error objects, not separate "code" and "message"
parameters.

This should fix the test in c05b5d8b by Mikeal Rogers.

http://groups.google.com/group/nodejs/browse_thread/thread/10fda8eaf7276642/e5d5147f2b666abd

createModule got removed as it was unnecessary and caused issues by
doing its own cache checks independent of loadModule. Internal modules
are now the only globally cached modules, all other modules are only
cached by inheriting their parent modules cache.

Credits: Module specific cache and a few other diffs by Blaine Cook

http://github.com/blaine/node/commit/431662d25c0db3096deb5f679ca73b1dd6bb8ae5
http://romeda.org/blog/2010/01/hot-code-loading-in-nodejs.html
http://thread.gmane.org/gmane.comp.lang.javascript.nodejs/1994

Broken on at least one platform http://pastie.org/808217

This reverts commit 704f394c.

for a %2.5 improvement in hello world HTTP score.

Fixes, among other things, a header overflow attack.

- assign 'GLOBAL' (and now 'global') inside src/node.js

- position for eventually allowing replacements to src/node.js for people
  like Kris Kowal who want the nice libev and libeio bindings but not
  necessarily node's choices of modules or promises.