Node.js stream behaviour illustrated.
github.com
Node.js stream behaviour illustrated.
1–6 of 6 posts
Re: Node.js stream behaviour illustrated.
#2the most misunderstood part of node. thanks for helping make it understandable
Re: Node.js stream behaviour illustrated.
#3streams are everywhere!
hope all of the streams will be unified by v1.0
Re: Node.js stream behaviour illustrated.
#4Could someone please enlighten me on how to connect both a readable and a writable stream.
For example I want to convert an image and then stream it to S3.
if I use knox https://github.com/LearnBoost/knox it has a way to read a stream from a file and then publish to s3.
But how can you take a stream from http://aheckmann.github.com/gm/ and stream it directly to knox or anything else for that matter?
Re: Node.js stream behaviour illustrated.
#5Could someone please enlighten me on how to connect both a readable and a writable stream. For example I want to convert an image and then stream it to S3. if I use knox https://github.com/LearnBoost/knox it has a way to read a stream from a file and then publish to s3. But how can you take a stream from http://aheckmann.github.com/gm/ and stream it directly to knox or anything else for that matter?
Take a look at the pipe() method. :-)
Re: Node.js stream behaviour illustrated.
#6Could someone please enlighten me on how to connect both a readable and a writable stream. For example I want to convert an image and then stream it to S3. if I use knox https://github.com/LearnBoost/knox it has a way to read a stream from a file and then publish to s3. But how can you take a stream from http://aheckmann.github.com/gm/ and stream it directly to knox or anything else for that matter?
something like gm(knox.getStream(...)).write(knox.putStream(...))
unfortunately gm doesn't expose it's streams nicely, so you have to pass them in.