Remove old stdout, stderr, stdin objects.

E.G. { "Content-Length": 10, "Content-Type": "text/html" } instead of
[["Content-Length", 10], ["Content-Type", "text/html"]].
The main reason for this change is object-creation efficiency.

This still needs testing and some further changes (like when receiving
multiple header lines with the same field-name, they are concatenated with a
comma but some headers ("Content-Length") should not be concatenated ; the
new header line should replace the old value).

Various thoughts on this subject:
http://groups.google.com/group/nodejs/browse_thread/thread/9a67bb32706d9efc#
http://four.livejournal.com/979640.html
http://mail.gnome.org/archives/libsoup-list/2009-March/msg00015.html

http://groups.google.com/group/nodejs/browse_thread/thread/16abfa87c32408f3

We have our node.js server monitored by monit, however it seems monit is pretty
agressive / quick about closing its connection and thus we've gotten into a
loop of errors like this:

    at #<a ServerResponse>.flush
    at #<a ServerResponse>.sendBody
    at [object Object].json
    at [object Object].[anonymous]
    at [object Object].[anonymous]
    at [object Object].[anonymous]
http.js:353: Socket is not open for writing
      connection.send(out, out.encoding);
                 ^

Below is a patch that basically cause flushMessageQueue to check the connection
state for each item in the queue rather than just a single time in the
beginning.

If the connection is open when the destructor is called it's a bug! Don't
want to try to compensate for bugs.

This function was removed in 368ea93b.

http://groups.google.com/group/nodejs/browse_thread/thread/13708eacedb40b36

In the case of stdin options.fd is 0, which is considered false, therefore fd
gets set to null intead of 0.
http://groups.google.com/group/nodejs/msg/80849f6aa0b0eaa0

More semantic, since the event will be emitted on connection error,
when the connection was ever established.

This was breaking the build on Macintosh.

discussion:
http://groups.google.com/group/nodejs/browse_thread/thread/11a920da4d0ed21d

Made API changes in evcom and had to make minor change src/net.cc to comply.

Similar to the error fixed in
9d3ed1bb.

Reported by Felix Geisendörfer.

This is same error that was fixed in 216fb3b9.

Reported by Felix Geisendörfer.

This is a temporary fix until V8 supports 64bit systems natively.