current streams are implicitly multi-topic: the 'error' event is in fact a topic
Am Dienstag, 15. Juli 2014 22:11:00 UTC+2 schrieb mscdex: > > On Monday, July 14, 2014 7:02:08 PM UTC-4, Chris Dickinson wrote: >> >> I just finished a recap of what I've been up to over the course of June, >> and what I'll be getting involved in in July -- specifically, I'll >> be working towards ownership of the streams subsystem. I wrote a post >> <http://neversaw.us/2014/07/13/june-recap/> detailing possible upcoming >> changes to streams, and I'd >> love to get your thoughts on it. >> >> > I can't say I'm a fan of the "multi-topic" streams. > > One thing that has kind of irked me about streams2 is/was the behavior of > .read(). It'd be nice to be able to just pass in a number of bytes and a > callback, then if (and only if) that many bytes are read, then callback is > called and pass a Buffer of that many bytes (no more, no less). > -- Job board: http://jobs.nodejs.org/ New group rules: https://gist.github.com/othiym23/9886289#file-moderation-policy-md Old group rules: 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 unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/56faa39f-8bd0-42e7-8395-965ca9d6f590%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
