lukechilds/node - node - Gitea: Git with a cup of tea

Tree: dcfb6d8286

isaacs 327b6e3e1d stream: Don't emit 'end' unless read() called This solves the problem of calling `readable.pipe(writable)` after the readable stream has already emitted 'end', as often is the case when writing simple HTTP proxies. The spirit of streams2 is that things will work properly, even if you don't set them up right away on the first tick. This approach breaks down, however, because pipe()ing from an ended readable will just do nothing. No more data will ever arrive, and the writable will hang open forever never being ended. However, that does not solve the case of adding a `on('end')` listener after the stream has received the EOF chunk, if it was the first chunk received (and thus, length was 0, and 'end' got emitted). So, with this, we defer the 'end' event emission until the read() function is called. Also, in pipe(), if the source has emitted 'end' already, we call the cleanup/onend function on nextTick. Piping from an already-ended stream is thus the same as piping from a stream that is in the process of ending. Updates many tests that were relying on 'end' coming immediately, even though they never read() from the req. Fix #4942		12 years ago
..
addons	test: modify async native test.js to test for #4820	12 years ago
disabled	Merge remote-tracking branch 'ry/v0.8' into master	12 years ago
fixtures	test: Fix debugger repl tests	12 years ago
gc	test: use the debug build of node-weak when necessary	13 years ago
internet	DNS: Support NAPTR queries	12 years ago
message	process: separate nextTick domain logic	12 years ago
pummel	test: Pass cli flags in pummel/test-regress-GH-892	12 years ago
simple	stream: Don't emit 'end' unless read() called	12 years ago
common.js	test: optionally set common.PORT via env variable	12 years ago