Node.js v0.2.4 and expected improvements in the v0.3.x branch
Last weekend can boast of two releases of Node.js: the next minor version in the v0.2.x branch and the official release of the v0.3.x branch. And even though the branch being developed is still marked as “unstable”, it expects significant improvements in performance, portability, and the addition of new features that you should know about right now. Moreover, this version is already fully operational. Also at the end of the topic is a bonus in the form of links to the Node.js v0.2.x and NPM package repositories (Node.js package manager).
Changes in version 0.2.4:
Corrections in the module working with the network:
Added the ability to start writing to the queue before the connection is completed.
In case of an unsuccessful attempt to close the connection, the write queue is no longer cleared.
Fixed bug with frequent checking of released descriptors in case of reaching the limit of connections ( Do not spin on accept () with EMFILE ).
The option --max-stack-size has been added to limit the maximum stack size of the V8 (V8 itself also supports options for limiting the size of the memory used by the engine).
Fixed errors in the child_process.exec () function related to the termination of the child process (now it happens using the SIGTERM signal, not SIGKILL).
Fixed incorrect release of resources when shutting down Node.
For those who love * nix also for convenient work with software at the expense of package managers, I have a small addition: I compiled on openSUSE BuildService packages for Node.js branches v0.2.x and NPM (Node.js package manager). Use on health ;-)