Currently, various internal streams have different events that indicate that the underlying resource has successfully been established:
fs streams use the open event once the file descriptor is availablenet.Sockets use the connect event once the socket has been establishedHttp2Streams use the ready event once the underlying http/2 session is established
I would like to suggest standardizing on emitting ready for all of these streams, i.e. emitting ready for fs streams and network sockets in addition to the event names they currently use.
If there are no objections, I think this makes for a good first contribution.
Currently, various internal streams have different events that indicate that the underlying resource has successfully been established:
fsstreams use theopenevent once the file descriptor is availablenet.Sockets use theconnectevent once the socket has been establishedHttp2Streams use thereadyevent once the underlying http/2 session is establishedI would like to suggest standardizing on emitting
readyfor all of these streams, i.e. emittingreadyforfsstreams and network sockets in addition to the event names they currently use.If there are no objections, I think this makes for a good first contribution.