Browse files

updated readable for streams2

  • Loading branch information...
1 parent 871444d commit 67a7807d32fb98e6214da8671723efbd1eaa4c25 @substack committed Jun 27, 2013
Showing with 30 additions and 17 deletions.
  1. +30 −17 readme.markdown
47 readme.markdown
@@ -124,32 +124,45 @@ Streams make programming in node simple, elegant, and composable.
# basics
-Streams are just
-that have a
-function and expected to act in a certain way depending if the stream is
-readable, writable, or both (duplex).
+There are 4 kinds of streams: readable, writable, transform, and duplex.
-To create a new stream, just do:
+There is also a compatibility mode for "classic streams" which were present in
+node 0.4 through 0.8.
-``` js
-var Stream = require('stream');
-var s = new Stream;
-This new stream doesn't yet do anything because it is neither readable nor
+All the kinds of streams use `.pipe()` to shuffle data around.
## readable
-To make that stream `s` into a readable stream, all we need to do is set the
-`readable` property to true:
+Let's make a readable stream!
``` js
-s.readable = true
+var Readable = require('stream').Readable;
+var rs = Readable();
+rs.push('beep ');
+$ node read.js
+beep boop
+`rs.push(null)` tells the consumer that `rs` is done outputting data.
+Note here that we pushed content to the readable stream `rs` before piping to
+`process.stdout`, but the complete message was still written.
+This is because when you `.push()` to a readable stream, the chunks you push are
+buffered until a consumer is ready to read them.
+# --------
Readable streams emit many `'data'` events and a single `'end'` event.
Your stream shouldn't emit any more `'data'` events after it emits the `'end'`

0 comments on commit 67a7807

Please sign in to comment.