|
|
|
'use strict';
|
|
|
|
require('../common');
|
|
|
|
var R = require('_stream_readable');
|
|
|
|
var W = require('_stream_writable');
|
|
|
|
var assert = require('assert');
|
|
|
|
|
|
|
|
var util = require('util');
|
|
|
|
|
|
|
|
var ondataCalled = 0;
|
|
|
|
|
|
|
|
function TestReader() {
|
|
|
|
R.apply(this);
|
|
|
|
this._buffer = Buffer.alloc(100, 'x');
|
|
|
|
|
|
|
|
this.on('data', function() {
|
|
|
|
ondataCalled++;
|
|
|
|
});
|
|
|
|
}
|
|
|
|
|
|
|
|
util.inherits(TestReader, R);
|
|
|
|
|
stream: There is no _read cb, there is only push
This makes it so that `stream.push(chunk)` is the only way to signal the
end of reading, removing the confusing disparity between the
callback-style _read method, and the fact that most real-world streams
do not have a 1:1 corollation between the "please give me data" event,
and the actual arrival of a chunk of data.
It is still possible, of course, to implement a `CallbackReadable` on
top of this. Simply provide a method like this as the callback:
function readCallback(er, chunk) {
if (er)
stream.emit('error', er);
else
stream.push(chunk);
}
However, *only* fs streams actually would behave in this way, so it
makes not a lot of sense to make TCP, TLS, HTTP, and all the rest have
to bend into this uncomfortable paradigm.
12 years ago
|
|
|
TestReader.prototype._read = function(n) {
|
|
|
|
this.push(this._buffer);
|
|
|
|
this._buffer = Buffer.alloc(0);
|
|
|
|
};
|
|
|
|
|
|
|
|
var reader = new TestReader();
|
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(function() {
|
|
|
|
assert.equal(ondataCalled, 1);
|
|
|
|
console.log('ok');
|
|
|
|
reader.push(null);
|
|
|
|
});
|
|
|
|
|
|
|
|
function TestWriter() {
|
|
|
|
W.apply(this);
|
|
|
|
this.write('foo');
|
|
|
|
this.end();
|
|
|
|
}
|
|
|
|
|
|
|
|
util.inherits(TestWriter, W);
|
|
|
|
|
|
|
|
TestWriter.prototype._write = function(chunk, enc, cb) {
|
|
|
|
cb();
|
|
|
|
};
|
|
|
|
|
|
|
|
var writer = new TestWriter();
|
|
|
|
|
|
|
|
process.on('exit', function() {
|
|
|
|
assert.strictEqual(reader.readable, false);
|
|
|
|
assert.strictEqual(writer.writable, false);
|
|
|
|
console.log('ok');
|
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
|
|
|
});
|