|
|
|
// Copyright Joyent, Inc. and other Node contributors.
|
|
|
|
//
|
|
|
|
// Permission is hereby granted, free of charge, to any person obtaining a
|
|
|
|
// copy of this software and associated documentation files (the
|
|
|
|
// "Software"), to deal in the Software without restriction, including
|
|
|
|
// without limitation the rights to use, copy, modify, merge, publish,
|
|
|
|
// distribute, sublicense, and/or sell copies of the Software, and to permit
|
|
|
|
// persons to whom the Software is furnished to do so, subject to the
|
|
|
|
// following conditions:
|
|
|
|
//
|
|
|
|
// The above copyright notice and this permission notice shall be included
|
|
|
|
// in all copies or substantial portions of the Software.
|
|
|
|
//
|
|
|
|
// THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
|
|
|
|
// OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
|
|
|
|
// MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN
|
|
|
|
// NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,
|
|
|
|
// DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR
|
|
|
|
// OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE
|
|
|
|
// USE OR OTHER DEALINGS IN THE SOFTWARE.
|
|
|
|
|
|
|
|
'use strict';
|
|
|
|
require('../common');
|
|
|
|
const assert = require('assert');
|
stream: Simplify flowing, passive data listening
Closes #5860
In streams2, there is an "old mode" for compatibility. Once switched
into this mode, there is no going back.
With this change, there is a "flowing mode" and a "paused mode". If you
add a data listener, then this will start the flow of data. However,
hitting the `pause()` method will switch *back* into a non-flowing mode,
where the `read()` method will pull data out.
Every time `read()` returns a data chunk, it also emits a `data` event.
In this way, a passive data listener can be added, and the stream passed
off to some other reader, for use with progress bars and the like.
There is no API change beyond this added flexibility.
12 years ago
|
|
|
|
|
|
|
const stream = require('stream');
|
|
|
|
const Readable = stream.Readable;
|
|
|
|
const Writable = stream.Writable;
|
stream: Simplify flowing, passive data listening
Closes #5860
In streams2, there is an "old mode" for compatibility. Once switched
into this mode, there is no going back.
With this change, there is a "flowing mode" and a "paused mode". If you
add a data listener, then this will start the flow of data. However,
hitting the `pause()` method will switch *back* into a non-flowing mode,
where the `read()` method will pull data out.
Every time `read()` returns a data chunk, it also emits a `data` event.
In this way, a passive data listener can be added, and the stream passed
off to some other reader, for use with progress bars and the like.
There is no API change beyond this added flexibility.
12 years ago
|
|
|
|
|
|
|
const totalChunks = 100;
|
|
|
|
const chunkSize = 99;
|
|
|
|
const expectTotalData = totalChunks * chunkSize;
|
|
|
|
let expectEndingData = expectTotalData;
|
stream: Simplify flowing, passive data listening
Closes #5860
In streams2, there is an "old mode" for compatibility. Once switched
into this mode, there is no going back.
With this change, there is a "flowing mode" and a "paused mode". If you
add a data listener, then this will start the flow of data. However,
hitting the `pause()` method will switch *back* into a non-flowing mode,
where the `read()` method will pull data out.
Every time `read()` returns a data chunk, it also emits a `data` event.
In this way, a passive data listener can be added, and the stream passed
off to some other reader, for use with progress bars and the like.
There is no API change beyond this added flexibility.
12 years ago
|
|
|
|
|
|
|
const r = new Readable({ highWaterMark: 1000 });
|
|
|
|
let chunks = totalChunks;
|
stream: Simplify flowing, passive data listening
Closes #5860
In streams2, there is an "old mode" for compatibility. Once switched
into this mode, there is no going back.
With this change, there is a "flowing mode" and a "paused mode". If you
add a data listener, then this will start the flow of data. However,
hitting the `pause()` method will switch *back* into a non-flowing mode,
where the `read()` method will pull data out.
Every time `read()` returns a data chunk, it also emits a `data` event.
In this way, a passive data listener can be added, and the stream passed
off to some other reader, for use with progress bars and the like.
There is no API change beyond this added flexibility.
12 years ago
|
|
|
r._read = function(n) {
|
|
|
|
if (!(chunks % 2))
|
|
|
|
setImmediate(push);
|
|
|
|
else if (!(chunks % 3))
|
|
|
|
process.nextTick(push);
|
|
|
|
else
|
|
|
|
push();
|
|
|
|
};
|
|
|
|
|
|
|
|
let totalPushed = 0;
|
stream: Simplify flowing, passive data listening
Closes #5860
In streams2, there is an "old mode" for compatibility. Once switched
into this mode, there is no going back.
With this change, there is a "flowing mode" and a "paused mode". If you
add a data listener, then this will start the flow of data. However,
hitting the `pause()` method will switch *back* into a non-flowing mode,
where the `read()` method will pull data out.
Every time `read()` returns a data chunk, it also emits a `data` event.
In this way, a passive data listener can be added, and the stream passed
off to some other reader, for use with progress bars and the like.
There is no API change beyond this added flexibility.
12 years ago
|
|
|
function push() {
|
|
|
|
const chunk = chunks-- > 0 ? Buffer.alloc(chunkSize, 'x') : null;
|
stream: Simplify flowing, passive data listening
Closes #5860
In streams2, there is an "old mode" for compatibility. Once switched
into this mode, there is no going back.
With this change, there is a "flowing mode" and a "paused mode". If you
add a data listener, then this will start the flow of data. However,
hitting the `pause()` method will switch *back* into a non-flowing mode,
where the `read()` method will pull data out.
Every time `read()` returns a data chunk, it also emits a `data` event.
In this way, a passive data listener can be added, and the stream passed
off to some other reader, for use with progress bars and the like.
There is no API change beyond this added flexibility.
12 years ago
|
|
|
if (chunk) {
|
|
|
|
totalPushed += chunk.length;
|
|
|
|
}
|
|
|
|
r.push(chunk);
|
|
|
|
}
|
|
|
|
|
|
|
|
read100();
|
|
|
|
|
|
|
|
// first we read 100 bytes
|
|
|
|
function read100() {
|
|
|
|
readn(100, onData);
|
|
|
|
}
|
|
|
|
|
|
|
|
function readn(n, then) {
|
|
|
|
console.error('read %d', n);
|
|
|
|
expectEndingData -= n;
|
|
|
|
(function read() {
|
|
|
|
const c = r.read(n);
|
stream: Simplify flowing, passive data listening
Closes #5860
In streams2, there is an "old mode" for compatibility. Once switched
into this mode, there is no going back.
With this change, there is a "flowing mode" and a "paused mode". If you
add a data listener, then this will start the flow of data. However,
hitting the `pause()` method will switch *back* into a non-flowing mode,
where the `read()` method will pull data out.
Every time `read()` returns a data chunk, it also emits a `data` event.
In this way, a passive data listener can be added, and the stream passed
off to some other reader, for use with progress bars and the like.
There is no API change beyond this added flexibility.
12 years ago
|
|
|
if (!c)
|
|
|
|
r.once('readable', read);
|
|
|
|
else {
|
|
|
|
assert.strictEqual(c.length, n);
|
stream: Simplify flowing, passive data listening
Closes #5860
In streams2, there is an "old mode" for compatibility. Once switched
into this mode, there is no going back.
With this change, there is a "flowing mode" and a "paused mode". If you
add a data listener, then this will start the flow of data. However,
hitting the `pause()` method will switch *back* into a non-flowing mode,
where the `read()` method will pull data out.
Every time `read()` returns a data chunk, it also emits a `data` event.
In this way, a passive data listener can be added, and the stream passed
off to some other reader, for use with progress bars and the like.
There is no API change beyond this added flexibility.
12 years ago
|
|
|
assert(!r._readableState.flowing);
|
|
|
|
then();
|
|
|
|
}
|
|
|
|
})();
|
|
|
|
}
|
|
|
|
|
|
|
|
// then we listen to some data events
|
|
|
|
function onData() {
|
|
|
|
expectEndingData -= 100;
|
|
|
|
console.error('onData');
|
|
|
|
let seen = 0;
|
stream: Simplify flowing, passive data listening
Closes #5860
In streams2, there is an "old mode" for compatibility. Once switched
into this mode, there is no going back.
With this change, there is a "flowing mode" and a "paused mode". If you
add a data listener, then this will start the flow of data. However,
hitting the `pause()` method will switch *back* into a non-flowing mode,
where the `read()` method will pull data out.
Every time `read()` returns a data chunk, it also emits a `data` event.
In this way, a passive data listener can be added, and the stream passed
off to some other reader, for use with progress bars and the like.
There is no API change beyond this added flexibility.
12 years ago
|
|
|
r.on('data', function od(c) {
|
|
|
|
seen += c.length;
|
|
|
|
if (seen >= 100) {
|
|
|
|
// seen enough
|
|
|
|
r.removeListener('data', od);
|
|
|
|
r.pause();
|
|
|
|
if (seen > 100) {
|
|
|
|
// oh no, seen too much!
|
|
|
|
// put the extra back.
|
|
|
|
const diff = seen - 100;
|
stream: Simplify flowing, passive data listening
Closes #5860
In streams2, there is an "old mode" for compatibility. Once switched
into this mode, there is no going back.
With this change, there is a "flowing mode" and a "paused mode". If you
add a data listener, then this will start the flow of data. However,
hitting the `pause()` method will switch *back* into a non-flowing mode,
where the `read()` method will pull data out.
Every time `read()` returns a data chunk, it also emits a `data` event.
In this way, a passive data listener can be added, and the stream passed
off to some other reader, for use with progress bars and the like.
There is no API change beyond this added flexibility.
12 years ago
|
|
|
r.unshift(c.slice(c.length - diff));
|
|
|
|
console.error('seen too much', seen, diff);
|
|
|
|
}
|
|
|
|
|
|
|
|
// Nothing should be lost in between
|
|
|
|
setImmediate(pipeLittle);
|
|
|
|
}
|
|
|
|
});
|
|
|
|
}
|
|
|
|
|
|
|
|
// Just pipe 200 bytes, then unshift the extra and unpipe
|
|
|
|
function pipeLittle() {
|
|
|
|
expectEndingData -= 200;
|
|
|
|
console.error('pipe a little');
|
|
|
|
const w = new Writable();
|
|
|
|
let written = 0;
|
stream: Simplify flowing, passive data listening
Closes #5860
In streams2, there is an "old mode" for compatibility. Once switched
into this mode, there is no going back.
With this change, there is a "flowing mode" and a "paused mode". If you
add a data listener, then this will start the flow of data. However,
hitting the `pause()` method will switch *back* into a non-flowing mode,
where the `read()` method will pull data out.
Every time `read()` returns a data chunk, it also emits a `data` event.
In this way, a passive data listener can be added, and the stream passed
off to some other reader, for use with progress bars and the like.
There is no API change beyond this added flexibility.
12 years ago
|
|
|
w.on('finish', function() {
|
|
|
|
assert.strictEqual(written, 200);
|
stream: Simplify flowing, passive data listening
Closes #5860
In streams2, there is an "old mode" for compatibility. Once switched
into this mode, there is no going back.
With this change, there is a "flowing mode" and a "paused mode". If you
add a data listener, then this will start the flow of data. However,
hitting the `pause()` method will switch *back* into a non-flowing mode,
where the `read()` method will pull data out.
Every time `read()` returns a data chunk, it also emits a `data` event.
In this way, a passive data listener can be added, and the stream passed
off to some other reader, for use with progress bars and the like.
There is no API change beyond this added flexibility.
12 years ago
|
|
|
setImmediate(read1234);
|
|
|
|
});
|
|
|
|
w._write = function(chunk, encoding, cb) {
|
|
|
|
written += chunk.length;
|
|
|
|
if (written >= 200) {
|
|
|
|
r.unpipe(w);
|
|
|
|
w.end();
|
|
|
|
cb();
|
|
|
|
if (written > 200) {
|
|
|
|
const diff = written - 200;
|
stream: Simplify flowing, passive data listening
Closes #5860
In streams2, there is an "old mode" for compatibility. Once switched
into this mode, there is no going back.
With this change, there is a "flowing mode" and a "paused mode". If you
add a data listener, then this will start the flow of data. However,
hitting the `pause()` method will switch *back* into a non-flowing mode,
where the `read()` method will pull data out.
Every time `read()` returns a data chunk, it also emits a `data` event.
In this way, a passive data listener can be added, and the stream passed
off to some other reader, for use with progress bars and the like.
There is no API change beyond this added flexibility.
12 years ago
|
|
|
written -= diff;
|
|
|
|
r.unshift(chunk.slice(chunk.length - diff));
|
|
|
|
}
|
|
|
|
} else {
|
|
|
|
setImmediate(cb);
|
|
|
|
}
|
|
|
|
};
|
|
|
|
r.pipe(w);
|
|
|
|
}
|
|
|
|
|
|
|
|
// now read 1234 more bytes
|
|
|
|
function read1234() {
|
|
|
|
readn(1234, resumePause);
|
|
|
|
}
|
|
|
|
|
|
|
|
function resumePause() {
|
|
|
|
console.error('resumePause');
|
|
|
|
// don't read anything, just resume and re-pause a whole bunch
|
|
|
|
r.resume();
|
|
|
|
r.pause();
|
|
|
|
r.resume();
|
|
|
|
r.pause();
|
|
|
|
r.resume();
|
|
|
|
r.pause();
|
|
|
|
r.resume();
|
|
|
|
r.pause();
|
|
|
|
r.resume();
|
|
|
|
r.pause();
|
|
|
|
setImmediate(pipe);
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
function pipe() {
|
|
|
|
console.error('pipe the rest');
|
|
|
|
const w = new Writable();
|
|
|
|
let written = 0;
|
stream: Simplify flowing, passive data listening
Closes #5860
In streams2, there is an "old mode" for compatibility. Once switched
into this mode, there is no going back.
With this change, there is a "flowing mode" and a "paused mode". If you
add a data listener, then this will start the flow of data. However,
hitting the `pause()` method will switch *back* into a non-flowing mode,
where the `read()` method will pull data out.
Every time `read()` returns a data chunk, it also emits a `data` event.
In this way, a passive data listener can be added, and the stream passed
off to some other reader, for use with progress bars and the like.
There is no API change beyond this added flexibility.
12 years ago
|
|
|
w._write = function(chunk, encoding, cb) {
|
|
|
|
written += chunk.length;
|
|
|
|
cb();
|
|
|
|
};
|
|
|
|
w.on('finish', function() {
|
|
|
|
console.error('written', written, totalPushed);
|
|
|
|
assert.strictEqual(written, expectEndingData);
|
|
|
|
assert.strictEqual(totalPushed, expectTotalData);
|
stream: Simplify flowing, passive data listening
Closes #5860
In streams2, there is an "old mode" for compatibility. Once switched
into this mode, there is no going back.
With this change, there is a "flowing mode" and a "paused mode". If you
add a data listener, then this will start the flow of data. However,
hitting the `pause()` method will switch *back* into a non-flowing mode,
where the `read()` method will pull data out.
Every time `read()` returns a data chunk, it also emits a `data` event.
In this way, a passive data listener can be added, and the stream passed
off to some other reader, for use with progress bars and the like.
There is no API change beyond this added flexibility.
12 years ago
|
|
|
console.log('ok');
|
|
|
|
});
|
|
|
|
r.pipe(w);
|
|
|
|
}
|