Files
node-v0.x-archive/test/simple
isaacs 88644eaa2d 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-02-28 17:38:17 -08:00
..
2012-02-20 13:29:11 +01:00
2010-02-25 11:41:11 -08:00
2012-06-11 15:51:23 -07:00
2012-12-14 10:52:30 -08:00
2012-01-17 19:45:09 +01:00
2011-11-25 01:25:38 +01:00
2012-01-24 00:30:28 +06:00
2012-01-17 19:45:09 +01:00
2012-01-17 19:45:09 +01:00
2011-03-14 17:37:05 -07:00
2011-03-14 17:37:05 -07:00
2012-12-14 17:46:23 -08:00
2011-11-01 22:26:52 +01:00
2011-11-01 22:26:52 +01:00
2012-02-18 15:34:57 -08:00
2011-10-22 14:14:40 +09:00
2011-10-22 14:14:40 +09:00
2011-10-22 14:14:40 +09:00
2012-12-14 17:46:23 -08:00
2012-12-14 17:46:23 -08:00
2012-01-17 19:45:09 +01:00
2012-06-29 17:29:32 +02:00
2012-07-04 13:45:14 +02:00
2012-01-17 19:45:09 +01:00
2011-03-14 17:37:05 -07:00
2012-01-09 11:20:22 -08:00
2013-02-28 23:11:47 +01:00
2012-12-14 10:52:30 -08:00
2011-08-09 13:55:04 -07:00
2011-03-14 17:37:05 -07:00
2012-05-10 16:49:37 +02:00
2012-12-14 10:52:26 -08:00
2011-10-05 18:51:06 -07:00