{"push_id":688396034,"size":1,"distinct_size":1,"ref":"refs/heads/http2_flow_writable","head":"614dad74c74664d0eb64d7bf65d0999a6a36b339","before":"34162f5aae112348b34fe98a8d583d4707c40af8","commits":[{"sha":"614dad74c74664d0eb64d7bf65d0999a6a36b339","author":{"email":"a8c456a6b54fc41d6e961143bac21b6e0910a8a8@apple.com","name":"Scott Mitchell"},"message":"HTTP/2 Flow Controller should use Channel.isWritable()\n\nMotivation:\nSee https://github.com/netty/netty/issues/3783\n\nModifications:\n- The DefaultHttp2RemoteFlowController should use Channel.isWritable() before attempting to do any write operations.\n- The Flow controller methods should no longer take ChannelHandlerContext. The concept of flow control is tied to a connection and we do not support 1 flow controller keeping track of multiple ChannelHandlerContext.\n\nResult:\nWrites are delayed until isWritable() is true. Flow controller interface methods are more clear as to ChannelHandlerContext restrictions.","distinct":true,"url":"https://api.github.com/repos/Scottmitch/netty/commits/614dad74c74664d0eb64d7bf65d0999a6a36b339"}]}