We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
http OutgoingMessage is missing some methods, properties and behaviours to make it "truly" "streamlike":
OutgoingMessage
destroyed
writableLength
writableHighWaterMark
writableCorked
writableObjectMode
cork()
uncork()
ERR_STREAM_DESTROYED
instanceof Writable
Furthermore the destroy event ordering does not seem to be fully consistent with the stream implementation (needs further investigation).
The text was updated successfully, but these errors were encountered:
Great initiative, definitely +1 to add all of these!
Sorry, something went wrong.
Is there some reason that OutgoingMessage is not an ancestor of Writable?
Performance
No branches or pull requests
http
OutgoingMessage
is missing some methods, properties and behaviours to make it "truly" "streamlike":destroyed
writableLength
(http: OutgoingMessage stream properties #29018)writableHighWaterMark
(http: OutgoingMessage stream properties #29018)writableCorked
writableObjectMode
(http: OutgoingMessage stream properties #29018)cork()
(http: outgoing cork #29053)uncork()
(http: outgoing cork #29053)ERR_STREAM_DESTROYED
(http: align with stream.Writable #31818)instanceof Writable
(issue http: OutgoingMessage instanceof Writable #28971)Furthermore the destroy event ordering does not seem to be fully consistent with the stream implementation (needs further investigation).
The text was updated successfully, but these errors were encountered: