[stream] Standardize a way for writable streams to do work after all data has been consumed.

[markstos]

There was a lot of discussion about this pre-fork:

nodejs/node-v0.x-archive#7631
nodejs/node-v0.x-archive#7348

Note that while waiting for an upstreaming fix, @TomFrost implemented a workaround that is published on npmjs.org:

https://www.npmjs.com/package/flushwritable

Perhaps it will be helpful in considering the issue.

[Fishrock123]

https://github.com/iojs/readable-stream may be a better place to discuss this. :)

[markstos]

@Fishrock123 I opened an issue in the readable-stream queue as you suggested:

nodejs/readable-stream#112

If this is the wrong place for stream issues now, this can be closed.

[vkurchatkin]

I'm +1. Also want _open and _close hooks for all streams

[tellnes]

+1 from me also.

@vkurchatkin What do you mean by _open and _close. Are you referring to fs streams which does fs.open?

[vkurchatkin]

Yeah, default open, close and destroy implementations which call hooks. Also auto-open, like in fs

[chrisdickinson]

Redirecting conversation to the readable-stream issue.