Are there any plans to deprecate Streams1?

99 views
Skip to first unread message

q2dg2b

unread,
Oct 11, 2014, 7:30:45 PM10/11/14
to nod...@googlegroups.com
Hello friends.

I see still there are many modules based on Streams1, when in Node 0.10 Streams2 implementation has appeared. Are there any plans about deprecating Stream1 in a far/near future?? If not, will both implementations coexist side by side?? Which should be officially recomended to use, then?

Thanks

P.D: I've seen in several places (http://stackoverflow.com/questions/21538812/what-is-streams3-in-node-js-and-how-does-it-differ-from-streams2, https://github.com/joyent/node/issues/5860) a "Streams3" implementation for Node 0.12, but I don't get the point...will it be a real change from Streams2 or is it only a marketing name??

zladuric

unread,
Oct 12, 2014, 4:22:11 AM10/12/14
to nod...@googlegroups.com
I'm not sure about 'streams1' though, but there are wrappers for it, such as https://www.npmjs.org/package/readable-wrap.

I don't think you need to wrap the writable part of the pipeline, since most of the issues with original streams were when readable stream starts emitting before you can set up a listener.

As for v3 to v2, as far as I'm aware, it should be backwards compatible., it's mostly about flowing/non-flowing mode thing.

Aria Stewart

unread,
Oct 12, 2014, 12:05:31 PM10/12/14
to nod...@googlegroups.com

> On 12 Oct 2014, at 04:22, zladuric <zlad...@gmail.com> wrote:
>
> I'm not sure about 'streams1' though, but there are wrappers for it, such as https://www.npmjs.org/package/readable-wrap.
>
> I don't think you need to wrap the writable part of the pipeline, since most of the issues with original streams were when readable stream starts emitting before you can set up a listener.
>
> As for v3 to v2, as far as I'm aware, it should be backwards compatible., it's mostly about flowing/non-flowing mode thing.

Which is actually blessing backward compatibility mode and integrating it, largely.

So streams1 will continue to work, modulo quirks around having to call resume to make them start, just like always. Streams2 will continue to work, as the 'minimal' part of the API.

Trevor Norris

unread,
Oct 13, 2014, 6:21:05 PM10/13/14
to nod...@googlegroups.com
On Saturday, October 11, 2014 4:30:45 PM UTC-7, q2dg2b wrote:
P.D: I've seen in several places (http://stackoverflow.com/questions/21538812/what-is-streams3-in-node-js-and-how-does-it-differ-from-streams2, https://github.com/joyent/node/issues/5860) a "Streams3" implementation for Node 0.12, but I don't get the point...will it be a real change from Streams2 or is it only a marketing name??

Streams 3 is more of a fix for streams 2. There was a discrepancy when using mixed streams which have been addressed. So there is no API change.
Reply all
Reply to author
Forward
0 new messages