Feature/better bio #5205

Closed
wants to merge 12 commits into from

7 participants

@indutny
Node.js Foundation member
isaacs and others added some commits Mar 28, 2013
@isaacs isaacs blog: Update linux binary tarball shasums
I just accidentally the binary release.
f1fa756
@isaacs isaacs blog: v0.11.0 release 1d17ced
@isaacs isaacs crypto: Pass options to ctor calls 7af075e
@TooTallNate TooTallNate repl: isSyntaxError() catches "strict mode" errors
Closes #5178.
085f9d6
@TooTallNate TooTallNate repl: use more readable RegExp syntax for spaces
This is just a cosmetic change really, nothing major.
55ea7cc
@mitar mitar querystring: Removing unnecessary binding
Binding of `http_parser` in querystring isn't used anywhere and should
be removed.
e5b90a1
@mhart mhart Ensure BAD domain example actually uses domain 440dcae
@isaacs isaacs tls: Destroy socket when encrypted side closes
The v0.8 Stream.pipe() method automatically destroyed the destination
stream whenever the src stream closed.  However, this caused a lot of
problems, and was removed by popular demand.  (Many userland modules
still have a no-op destroy() method just because of this.) It was also
very hazardous because this would be done even if { end: false } was
passed in the pipe options.

In v0.10, we decided that the 'close' event and destroy() method are
application-specific, and pipe() doesn't automatically call destroy().
However, TLS actually depended (silently) on this behavior.  So, in this
case, we should just go ahead and destroy the thing when close happens.

Closes #5145
164d5b3
@arhart arhart test: test intended code-paths
The tests did not agree with the test comments. Tests first and second
were both testing the !state.reading case. Now second tests the
state.reading && state.length case.

Fixes nodejs/node-v0.x-archive#5183
db8ce89
@isaacs isaacs http client: Ensure socket cleanup on response end
If an http response has an 'end' handler that throws, then the socket
will never be released back into the pool.

Granted, we do NOT guarantee that throwing will never have adverse
effects on Node internal state.  Such a guarantee cannot be reasonably
made in a shared-global mutable-state side-effecty language like
JavaScript.  However, in this case, it's a rather trivial patch to
increase our resilience a little bit, so it seems like a win.

There is no semantic change in this case, except that some event
listeners are removed, and the `'free'` event is emitted on nextTick, so
that you can schedule another request which will re-use the same socket.
From the user's point of view, there should be no detectable difference.

Closes #5107
234fb12
@mscdex mscdex src: remove unused variables 38106da
@indutny indutny crypto: use better memory BIO implementation 1169702
@indutny
Node.js Foundation member

Wrong base.

@indutny indutny closed this Apr 3, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment