You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Why http2session.socket.bufferSize is always zero? #21631
This is due to the special way that http2 sessions interact with the socket at the native (c++) layer rather than the javascript layer. The socket object's js interface is not used directly, and therefore the bufferSize is not set. We can investigate a way of enabling that.
As Http2Session and Http2Stream have internally maintained writeQueueSize which is actually kLastWriteQueueSize, I think, maybe we can make bufferSize work on http2 module itself.
Activity
jasnell commentedon Aug 10, 2018
This is due to the special way that http2 sessions interact with the socket at the native (c++) layer rather than the javascript layer. The socket object's js interface is not used directly, and therefore the bufferSize is not set. We can investigate a way of enabling that.
jasnell commentedon Sep 21, 2018
@addaleax ... do you have any thoughts on how we could make
bufferSizework on a socket bound to an http2session?oyyd commentedon Oct 16, 2018
According to the
netmodule,bufferSizeis:node/lib/net.js
Line 518 in deaddd2
As
Http2SessionandHttp2Streamhave internally maintainedwriteQueueSizewhich is actuallykLastWriteQueueSize, I think, maybe we can makebufferSizework on http2 module itself.http2: add Http2Stream.bufferSize
http2: add Http2Stream.bufferSize
apapirovski commentedon Nov 29, 2018
The PR for this has landed so I believe we can close this.
http2: add Http2Stream.bufferSize