Repository navigation
stream: standardize async initialization #29314
Description
Activity
- changed the title
[-]stream: provide a _construct end-point for streams with async initialization.[/-][+]stream: standardize async initialization.[/+]on Aug 25, 2019 - changed the title
[-]stream: standardize async initialization.[/-][+]stream: standardize async initialization[/+]on Aug 25, 2019 Here is a proposal implementation. Don't think I can get much further without some feedback.
19 remaining items
- added 2 commits that reference this issue
on May 25, 2020 This has landed.
Some streams (e.g.
fsandnet) need to first asynchronously create resources before they can perform any work. Currently this is implemented in the different stream implementations which both makes things more difficult and error prone (e.g.'open'and'ready'are emitted after'close'). I suggest we provide a standardized way of achieving this.This would allow further simplification and improved consistency for various stream implementations such as
fsandnetstream.I propose the following API for this:
stream._construct(cb)endpoint (similar to_destroy(cb)).stream.readyproperty indicating whether the stream is ready (currently this is calledpendingin some implementations). IncludingreadableReadyandwritableReadyaccessors.'ready'event (currently this is called'open'in some implementations).See, nxtedition#2 for proof of concept.