|
|
|
'use strict';
|
|
|
|
require('../common');
|
|
|
|
const assert = require('assert');
|
|
|
|
|
|
|
|
const Readable = require('stream').Readable;
|
|
|
|
|
|
|
|
test1();
|
|
|
|
test2();
|
|
|
|
|
|
|
|
function test1() {
|
|
|
|
const r = new Readable();
|
|
|
|
|
|
|
|
// should not end when we get a Buffer.alloc(0) or '' as the _read
|
|
|
|
// result that just means that there is *temporarily* no data, but to
|
|
|
|
// go ahead and try again later.
|
|
|
|
//
|
|
|
|
// note that this is very unusual. it only works for crypto streams
|
|
|
|
// because the other side of the stream will call read(0) to cycle
|
|
|
|
// data through openssl. that's why setImmediate() is used to call
|
|
|
|
// r.read(0) again later, otherwise there is no more work being done
|
|
|
|
// and the process just exits.
|
|
|
|
|
|
|
|
const buf = Buffer.alloc(5, 'x');
|
|
|
|
let reads = 5;
|
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
|
|
|
r._read = function(n) {
|
|
|
|
switch (reads--) {
|
|
|
|
case 5:
|
|
|
|
return setImmediate(function() {
|
|
|
|
return r.push(buf);
|
|
|
|
});
|
|
|
|
case 4:
|
|
|
|
setImmediate(function() {
|
|
|
|
return r.push(Buffer.alloc(0));
|
|
|
|
});
|
|
|
|
return setImmediate(r.read.bind(r, 0));
|
|
|
|
case 3:
|
|
|
|
setImmediate(r.read.bind(r, 0));
|
|
|
|
return process.nextTick(function() {
|
|
|
|
return r.push(Buffer.alloc(0));
|
|
|
|
});
|
|
|
|
case 2:
|
|
|
|
setImmediate(r.read.bind(r, 0));
|
|
|
|
return r.push(Buffer.alloc(0)); // Not-EOF!
|
|
|
|
case 1:
|
|
|
|
return r.push(buf);
|
|
|
|
case 0:
|
|
|
|
return r.push(null); // EOF
|
|
|
|
default:
|
|
|
|
throw new Error('unreachable');
|
|
|
|
}
|
|
|
|
};
|
|
|
|
|
|
|
|
const results = [];
|
|
|
|
function flow() {
|
|
|
|
let chunk;
|
|
|
|
while (null !== (chunk = r.read()))
|
|
|
|
results.push(chunk + '');
|
|
|
|
}
|
|
|
|
r.on('readable', flow);
|
|
|
|
r.on('end', function() {
|
|
|
|
results.push('EOF');
|
|
|
|
});
|
|
|
|
flow();
|
|
|
|
|
|
|
|
process.on('exit', function() {
|
|
|
|
assert.deepStrictEqual(results, [ 'xxxxx', 'xxxxx', 'EOF' ]);
|
|
|
|
console.log('ok');
|
|
|
|
});
|
|
|
|
}
|
|
|
|
|
|
|
|
function test2() {
|
|
|
|
const r = new Readable({ encoding: 'base64' });
|
|
|
|
let reads = 5;
|
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
|
|
|
r._read = function(n) {
|
|
|
|
if (!reads--)
|
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
|
|
|
return r.push(null); // EOF
|
|
|
|
else
|
|
|
|
return r.push(Buffer.from('x'));
|
|
|
|
};
|
|
|
|
|
|
|
|
const results = [];
|
|
|
|
function flow() {
|
|
|
|
let chunk;
|
|
|
|
while (null !== (chunk = r.read()))
|
|
|
|
results.push(chunk + '');
|
|
|
|
}
|
|
|
|
r.on('readable', flow);
|
|
|
|
r.on('end', function() {
|
|
|
|
results.push('EOF');
|
|
|
|
});
|
|
|
|
flow();
|
|
|
|
|
|
|
|
process.on('exit', function() {
|
|
|
|
assert.deepStrictEqual(results, [ 'eHh4', 'eHg=', 'EOF' ]);
|
|
|
|
console.log('ok');
|
|
|
|
});
|
|
|
|
}
|