On Monday, March 18, 2013 11:06:48 AM UTC-7, Sigurgeir Jonsson wrote: > > The new streams have excellent support for high/low watermarks and > auto-pausing/resuming, but the documentation confuses me a little... > particularly the read method. > > When I read the new docs for the first time I was under the impression > that the optimal way to become a user of a stream is to write loops around > the read functio. However in practice I find myself simply writing custom > writeStreams and use the callback to control upstream pressure (in addition > to source Watermarks if needed). Here is an example where I move the > output to a queue that executes a custom function in parallel (i.e. > uploading to a database) https://gist.github.com/ZJONSSON/5189249 > > Are there any benefits to using the read method directly on a stream vs. > piping to a custom Writable stream? >
-- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
