Merged
Merged
Conversation
| In other words, many lower-level protocols (such as TCP/IP) may choose | ||
| to only emit this for a fatal transmission error once and will thus | ||
| likely close (terminate) the stream in response. | ||
| It this is a fatal error that results in the stream being closed, it |
| }); | ||
| ``` | ||
|
|
||
| This event SHOULD be emitted once every time the buffer become full |
|
|
||
| The `pipe` event will be emitted whenever a readable stream is `pipe()`d | ||
| into this stream. | ||
| Event event receives a single `ReadableStreamInterface` argument for the |
| only deal with data transmission and may choose | ||
| to only emit this for a fatal transmission error once and will thus | ||
| likely close (terminate) the stream in response. | ||
| It this is a fatal error that results in the stream being closed, it |
| * | ||
| * This event SHOULD be emitted once or never at all, depending on whether | ||
| * the stream ever terminates. | ||
| * It SHOULD NOT be emitted afer a previous `close` event. |
| * | ||
| * This event SHOULD be emitted once or never at all, depending on whether | ||
| * the stream ever terminates. | ||
| * It SHOULD NOT be emitted afer a previous `close` event. |
|
|
||
| This event SHOULD be emitted once or never at all, depending on whether | ||
| the stream ever terminates. | ||
| It SHOULD NOT be emitted afer a previous `close` event. |
|
|
||
| This event SHOULD be emitted once or never at all, depending on whether | ||
| the stream ever terminates. | ||
| It SHOULD NOT be emitted afer a previous `close` event. |
jsor approved these changes Mar 7, 2017
Merged
clue deleted the event-semantics branch
March 10, 2017 22:03
Merged
Closed
Merged