2015-05-19 13:00:06 +02:00
|
|
|
'use strict';
|
2013-01-24 02:52:45 +01:00
|
|
|
var common = require('../common');
|
|
|
|
var assert = require('assert');
|
|
|
|
var Readable = require('stream').Readable;
|
|
|
|
var r = new Readable();
|
|
|
|
var N = 256 * 1024;
|
|
|
|
|
|
|
|
// Go ahead and allow the pathological case for this test.
|
|
|
|
// Yes, it's an infinite loop, that's the point.
|
|
|
|
process.maxTickDepth = N + 2;
|
|
|
|
|
|
|
|
var reads = 0;
|
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.
2013-03-01 00:32:32 +01:00
|
|
|
r._read = function(n) {
|
2013-01-24 02:52:45 +01:00
|
|
|
var chunk = reads++ === N ? null : new Buffer(1);
|
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.
2013-03-01 00:32:32 +01:00
|
|
|
r.push(chunk);
|
2013-01-24 02:52:45 +01:00
|
|
|
};
|
|
|
|
|
|
|
|
r.on('readable', function onReadable() {
|
|
|
|
if (!(r._readableState.length % 256))
|
|
|
|
console.error('readable', r._readableState.length);
|
|
|
|
r.read(N * 2);
|
|
|
|
});
|
|
|
|
|
|
|
|
var ended = false;
|
|
|
|
r.on('end', function onEnd() {
|
|
|
|
ended = true;
|
|
|
|
});
|
|
|
|
|
|
|
|
r.read(0);
|
|
|
|
|
|
|
|
process.on('exit', function() {
|
|
|
|
assert(ended);
|
|
|
|
console.log('ok');
|
|
|
|
});
|