Re: [nodejs] zlib stream.write callback

I see that zlib streams accept a callback to their write method, which will
be called when the input buffer is completely read (I'm guessing). But I
don't see documentation of that in the API docs. Is it safe to use this
feature?

Kevin

No, it is going away in 0.10, with the stream API cleanup.

Cool - are new-style streams and old-style streams going to coexist in
0.10, or is everything being moved over to new-style?

Kevin

Hmmm...

I'd like very much to have a way to determine when zlib is done with a
buffer, but without using the callback it appears to be a black hole of
sorts for whatever I put in.

I'm all for allocating like mad and using the GC to manage things, but I
would also like to have the option of micro-managing buffers if I choose.
It's systems programming, right? : )

Kevin

Ok, fair enough. Writable stream write() callbacks landed on streams2 branch.

wait, what? *all* readable streams have a write() callback now?

-Mikeal

No, all *writable* streams in core will, and the Writable base class will
provide it.

Too nice : )

I could be misguided, but I find that I gravitate toward low-level IO, like
the interface that fs provides. The cool thing about fs (not the streams,
but the posix functions), is that I can wrap them in whatever abstraction
makes sense at the time. I can create my own stream classes around it, or
I can make it callback-based or promise-based if I prefer. At the lowest
level, it's pure simplicity:

read:
fill this buffer with this many bytes, please, and call this
function when yer done (and let me know how much you
wrote).

write:
write this many bytes from this buffer and let me know when
you're done with said buffer.


Kevin