Add key.code and key.sequence -mad props go out to @TooTallNate
It's backwards compatible with the old waf build system. If you want to compile just the debug build, run `make -C out BUILDTYPE=Debug` instead. Fixes #2615.
* Update V8 to 3.8.8 * Install node-waf by default (Fedor Indutny) * crypto: Add ability to turn off PKCS padding (Ingmar Runge) * v8: implement VirtualMemory class on SunOS (Ben Noordhuis) * Add cluster.setupMaster (Andreas Madsen) * move `path.exists*` to `fs.exists*` (Maciej Małecki) * typed arrays: set class name (Ben Noordhuis) * libuv bug fixes (Igor Zinkovsky, Ben Noordhuis, Dan VerWeire)
Change formatProperty in util.js to use Object.getOwnPropertyDescriptor instead of __lookup[GS]etter__. Use the cached value from the descriptor to reduce number of property lookups from 3 to 1. Fallback to standard lookup if the descriptor is empty. This doesn't ever happen with normal JS objects (this function is called only when the key exists) but apparently does with Node's custom ENV interface. Fixes: #2109.
As RFC 2616 says we should, assume that servers will provide a persistent connection by default. > A significant difference between HTTP/1.1 and earlier versions of > HTTP is that persistent connections are the default behavior of any > HTTP connection. That is, unless otherwise indicated, the client > SHOULD assume that the server will maintain a persistent connection, > even after error responses from the server. > HTTP/1.1 applications that do not support persistent connections MUST > include the "close" connection option in every message. Fixes #2436.
`path.exists*` functions show a deprecation warning and call functions from `fs`. They should be removed later. test: fix references to `path.exists*` in tests test fs: add test for `fs.exists` and `fs.existsSync` doc: reflect moving `path.exists*` to `fs`
Removed during the early stages of node 0.5 refactoring to libuv.