Closed louiscryan closed 8 years ago
Seems reasonable enough to me. @bradfitz does the Golang implementation of this include padding data in dataIn/dataOut?
Sounds good to me. My current implementation does not include padding in the dataIn
number. I actually suspect Go's implementation is wrong here with respect to flow control, now that @louiscryan mentions it. I'll double-check.
We never generate padding out, so that field is easy to compute.
Yeah, the same is true with the Python implementation (re: generating padding out). I feel more confident that we're getting the arithmetic right though.
Ok, cool, let's add this too.
Added in master.
Padding counts against flow-control window and should be accounted for.
Currently spec has dataIn / dataOut which does not include padding. We've seen issues with padding arithmetic omissions causing flow-control drift.
https://github.com/netty/netty/issues/5434
Add paddingIn / out per stream?