* print undefined on undefined values in REPL (Nathan Rajlich)
* doc improvements (koichik, seebees, bnoordhuis,
Maciej Małecki, Jacob Kragh)
* support native addon loading in windows (Bert Belder)
* rename getNetworkInterfaces() to networkInterfaces() (bnoordhuis)
* add pending accepts knob for windows (igorzi)
* http.request(url.parse(x)) (seebees)
* #1929 zlib Respond to 'resume' events properly (isaacs)
* stream.pipe: Remove resume and pause events
* test fixes for windows (igorzi)
* build system improvements (bnoordhuis)
* #1936 tls: does not emit 'end' from EncryptedStream (koichik)
* #758 tls: add address(), remoteAddress/remotePort
* #1399 http: emit Error object after .abort() (bnoordhuis)
* #1999 fs: make mkdir() default to 0777 permissions (bnoordhuis)
* #2001 fix pipe error codes
* #2002 Socket.write should reset timeout timer
* stdout and stderr are blocking when associated with file too.
* remote debugger support on windows (Bert Belder)
* convenience methods for zlib (Matt Robenolt)
* process.kill support on windows (igorzi)
* process.uptime() support on windows (igorzi)
* Return IPv4 addresses before IPv6 addresses from getaddrinfo
* util.inspect improvements (Nathan Rajlich)
* cluster module api changes
* Downgrade V8 to 3.6.6.6
Download: http://nodejs.org/dist/v0.6.0/node-v0.6.0.tar.gz
Windows Executable: http://nodejs.org/dist/v0.6.0/node.exe
Website: http://nodejs.org/docs/v0.6.0/
Documentation: http://nodejs.org/docs/v0.6.0/api/
--
Job Board: http://jobs.nodejs.org/
Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nod...@googlegroups.com
To unsubscribe from this group, send email to
nodejs+un...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
npm (1.0.103) won't install with Node 0.6.0, as it has a dependency on 0.4 or 0.5. There's an issue open (https://github.com/isaacs/npm/issues/1657), or for the desperate a quick change to npm's package.json node engine dependency declaration is all that is needed.
--
Job Board: http://jobs.nodejs.org/
Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nod...@googlegroups.com
To unsubscribe from this group, send email to
nodejs+un...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
Sent from my Windows Phone
From: Ryan Dahl
Sent: 11/5/2011 2:27 AM
To: nodejs
Subject: [nodejs] Node v0.6.0
Joaquim Serafim
Kind regards
---
Thomas FRITZ
web http://fritzthomas.com
twitter http://twitter.com/thomasf
2011/11/7 joaquim.serafim <joaquim...@gmail.com>:
node.js:201
throw e; // process.nextTick error, or 'error' event on first tick
^
Error: No such module
at Object.<anonymous> (/usr/lib/node_modules/npm/lib/utils/config-defs.js:5:21)
at Module._compile (module.js:432:26)
at Object..js (module.js:450:10)
at Module.load (module.js:351:31)
at Function._load (module.js:310:12)
at Module.require (module.js:357:17)
at require (module.js:368:17)
at Object.<anonymous> (/usr/lib/node_modules/npm/lib/utils/ini.js:40:18)
at Module._compile (module.js:432:26)
at Object..js (module.js:450:10)
Any documentation explaining the cluster module in more detail?
--
regards
---
Thomas FRITZ
web http://fritzthomas.com
twitter http://twitter.com/thomasf
2011/11/11 Rambo <demi...@gmail.com>:
> Maybe I'm not looking for documentation, but perhaps an article explaining
> how to use it with real world examples? I'm not familiar with that api at
> all.
>
Guy that ran the benchmarks here. There are a number of things at play here:
1) We now use native Windows APIs instead of Cygwin's emulation layer.
2) Asynchronous file I/O on Windows is in a much better shape than on
the Unices.
3) The drop in performance may have been local to the system I ran the
benchmark on. The 0.4 and 0.6 numbers on my local system, for example,
are much closer (but then my local system isn't high-end server gear).
Incidentally, I profiled our I/O benchmark yesterday. It's not that
raw I/O performance has dropped, it's that the overhead of getting the
data into JS land seems to have increased.
Track https://github.com/joyent/node/issues/2071 if you want to keep posted.