The Streams implementation now works the way you thought it already should,without introducing any changes to the API. Basically this means no moregetting stuck in "old mode", there are only streams that are flowing or not.
Streams now support the use of cork and uncork mechanisms to preventflushing writes out to the system if an application is going to beperforming many writes in a row. There is an implicit uncork performed whenyou end a writable stream.
HTTP
maxSockets are no longer limited to 5. The default is now set toInfinity with the developer and the operating system given control overhow many simultaneous connections an application can keep open to a givenhost.
Proper KeepAlive support means that sockets will stay open until theytimeout at the configured time, are closed by the remote side, or theprocess exits. Developer's no longer have to make sure requests have beenpipelined to keep the socket open, or use an>
Developers can also now explicitly flushHeaders to ensure time to firstbyte is low and proxied connections are held open.
Cluster
Now has two modes of operation, the new default is a round robindistribution mechanism where the master accepts new connections anddistributes them to your workers. If you want you can still opt back intothe old method where your workers are responsible for acception connections.
TLS
We have the new TLSWrap mechanism under the hood, this eliminates quite afew of the hops back and forth between JavaScript and our C++implementations.
Added APIs for asynchronous SNI callbacks, OCSP stapling, and storageevents.
Buffer
We use a more accurate mechanism for allocating memory for buffers now,which means you'll see less overhead and impact from holding onto to smallslices of Buffers. This reduces the amount of memory pressure on the system,which means GC runs are quicker, which means Node.js is on CPU less, andthus lower latency for your applications.
child_process
spawnSync/execSync have been added to facilitate synchronous childprocesses, warning your node process won't make forward progress whilewaiting for the child to exit, caveat emptor!
Crypto
Added APIs for loading custom engines for use with compiled in OpenSSL.
More APIs support supplying the pass phrases.
Added APIs for RSA public/private key encryption/decryption.
VM
The module is now based on the Contextify module, which shares values fromthe sandbox to avoid missing changes inside the execution from appearing inthe parent context.
初步支持 ECMAScript Internationalization API 1.0(ECMA-402)
By default, Node.js v0.12.0 binaries are shipped with ECMA-402 support,but only for the English language. In other words, the ECMA-402 API isworking as you would expect, but only data for the English language isincluded. You can find more info on how to include more languages inthe Wiki.
相关资源:
源代码:http://nodejs.org/dist/v0.12.0/node-v0.12.0.tar.gz
Macintosh Installer (Universal): http://nodejs.org/dist/v0.12.0/node-v0.12.0.pkg
Windows Installer: http://nodejs.org/dist/v0.12.0/node-v0.12.0-x86.msi
Windows x64 Installer: http://nodejs.org/dist/v0.12.0/x64/node-v0.12.0-x64.msi
Windows x64 Files: http://nodejs.org/dist/v0.12.0/x64/
Linux 32-bit Binary: http://nodejs.org/dist/v0.12.0/node-v0.12.0-linux-x86.tar.gz
Linux 64-bit Binary: http://nodejs.org/dist/v0.12.0/node-v0.12.0-linux-x64.tar.gz
Solaris 32-bit Binary: http://nodejs.org/dist/v0.12.0/node-v0.12.0-sunos-x86.tar.gz
Solaris 64-bit Binary: http://nodejs.org/dist/v0.12.0/node-v0.12.0-sunos-x64.tar.gz