Skip to content

Documentation/Add 'close' events to fs.ReadStream, fs.WriteStream, etc per Issue #6484 #6499

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
jennabelle wants to merge 8 commits into from
Closed

Documentation/Add 'close' events to fs.ReadStream, fs.WriteStream, etc per Issue #6484 #6499

Changes from 1 commit
Commits
Show all changes
8 commits
Select commit Hold shift + click to select a range
9d48b5d
Add 'close' events to fs.ReadStream and fs.WriteSTream
May 1, 2016
ff217a8
Add 'close' event to stream.Writable per Issue #6484
May 1, 2016
827dfcb
Add #### prefix to Event: 'close' and backticks to 'close' similar to…
May 1, 2016
57aa9e6
Add more specifics to 'close' events for fs.ReadStream and fs.WriteSt…
May 1, 2016
439df4b
Fix/Changed 'close' event from 'fs.ReadStream' to 'fs.WriteStream'
May 1, 2016
b2a0db1
wrapped long lines at 80 chars, reworded
May 2, 2016
bcc8bd2
including the 'close' event as optional
May 2, 2016
8cdf720
add 'close' event as optional in stream.Readable
May 2, 2016
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Add #### prefix to Event: 'close' and backticks to 'close' similar to… 
… stream.Readable event: 'close' section
  • Loading branch information
Jenna Vuong committed May 1, 2016
commit 827dfcbf8dd3ceb7d38c64be220248922c0ae43c
4 changes: 2 additions & 2 deletions doc/api/stream.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -573,11 +573,11 @@ Examples of writable streams include:
* [child process stdin][]
* [`process.stdout`][], [`process.stderr`][]

Event: 'close'
#### Event: 'close'

Emitted when the stream and any of its underlying resources (a file descriptor, for example) have been closed. The event indicates that no more events will be emitted, and no further computation will occur.
Copy link
Copy Markdown
Member

@mcollina mcollina May 2, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How does this differs from 'end'?
Should a user expect 'close' or 'end' to proceed? Which one happens first?

I will also move this block after 'end', meaning that 'end' is the preferred way of waiting for the end of a stream.

Copy link
Copy Markdown
Contributor Author

@jennabelle jennabelle May 2, 2016 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mcollina

I hesitate to move the 'Event: 'close'' block to after the 'Event: 'end'' block because these events seem to be in alphabetical order for better user experience.

The difference between 'close' and 'end' events:

  1. 'close' event - Whatever it is tied to, for example a stream, it is done now. This event comes from the fs.close() method and is optional. Not all streams emit this event.
  2. 'end' event - Waits for the current data to finish buffering. means no more data will be emitted. This event is tied to the end() function on Streams.


Not all streams will emit the 'close' event.
Not all streams will emit the `'close'` event.
Copy link
Copy Markdown
Member

@mcollina mcollina May 2, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I will say this is an optional event for implementors.


#### Event: 'drain'

Expand Down