Node v0.2.4

[Ryan Dahl]

2010.10.24, Version 0.2.4

* Add --eval to command line options (TJ Holowaychuk)

* net fixes
- TCP clients buffer writes before connection
- Don't flush net writeQueue on end() if its still connecting
(Joshua Peek)
- Do not spin on aceept() with EMFILE

* Add --max-stack-size flag. (Tom Hughes)

* Fixes to child_process.exec (timeouts and proper termination)
Default to SIGTERM instead of SIGKILL.

* Add signal handlers so we clean up before exiting. (Tom Hughes)

Download: http://nodejs.org/dist/node-v0.2.4.tar.gz

Website: http://nodejs.org/docs/v0.2.4/

Documentation: http://nodejs.org/docs/v0.2.4/api.html

[rtweed]

Just a suggestion - could http://nodejs.org/dist/node-latest.tar.gz be
maintained as a matter of course to hold a copy of the latest stable
build? It currently seems to contain 0.2.1 judging by the date (10
Sep). It would be great to have a single named file that you could
guarantee you get the latest, eg for automated systems, installers etc

Rob

[Ryan Dahl]

On Thu, Oct 28, 2010 at 10:29 AM, rtweed <rob....@gmail.com> wrote:
> Just a suggestion - could http://nodejs.org/dist/node-latest.tar.gz be
> maintained as a matter of course to hold a copy of the latest stable
> build?  It currently seems to contain 0.2.1 judging by the date (10
> Sep).  It would be great to have a single named file that you could
> guarantee you get the latest, eg for automated systems, installers etc

Sure. Updated.

[Stephen Belanger]

I don't think automating node upgrades is particularly safe quite yet...

--
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.

[rtweed]

Thanks Ryan!

On Oct 28, 6:34 pm, Ryan Dahl <r...@tinyclouds.org> wrote:

[Stephen Belanger]

Perhaps we could have a "latest" archive for each major release like this;

http://nodejs.org/dist/node-0.2.x-latest.tar.gz

That way it only auto upgrades to the same major release to avoid core API changes that break your system, you'd just get bugfixes as they roll out.

[Trent Mick]

Stephen,

You could script that by parsing the HTML from http://nodejs.org/dist/
fairly easily. Not the most robust system, tho, I'll grant.

Could also have a releases.json or something like that that gave those
details in a more structured format. Don't want to overdesign the
release process tho.

Trent

--
Trent Mick

[Stephen Belanger]

I don't really need it myself, just making suggestions that'd help the other guy. I try to avoid automated upgrades on unstable systems. ;)