{"push_id":886169060,"size":1,"distinct_size":1,"ref":"refs/heads/0.5.x","head":"96b923464eb1355c485c2f524886ebd70b7a13c6","before":"5d8243ad5f952eec8dcdef1a9f00b7b4dd0f0fc5","commits":[{"sha":"96b923464eb1355c485c2f524886ebd70b7a13c6","author":{"email":"170d84963e98e44aa9c5756a5ca97e3ce2dff8ab@netflix.com","name":"Nitesh Kant"},"message":"Race-condition with HTTP persistent connections.\n\nFor HTTP persistent connections, on the server, there was a `ConnectionInputSubscriber` subscribed to the connection input which managed the demand for the connection input. The demand generated by HTTP content is relayed as-is to the connection. This would end up in a state if a content subscriber over-subscribes the data on the connection is read without an existing subscriber and hence disposed.\n\nThis change manages concatenated `ConnectionInputSubscriber`s and completes the previous subscriber when a new one arrives. This would make sure that the data is buffered when there is no subscriber existing and relayed when one arrives, in case of over-subscription.\n Http server now instead of managing requests via backpressure, now does multiple subscriptions and hence the backpressure is managed upstream at the channel (due to absence/presence of a subscriber)","distinct":true,"url":"https://api.github.com/repos/NiteshKant/RxNetty/commits/96b923464eb1355c485c2f524886ebd70b7a13c6"}]}