{"push_id":863853457,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"07c150868f7833b8cf659cf888aa3febd8c2ca8a","before":"19d24e21568ec8e04da748dbe815f046a327f274","commits":[{"sha":"07c150868f7833b8cf659cf888aa3febd8c2ca8a","author":{"email":"6c711b0d09d9dffbc1118d511ee214647fa2a34f@fb.com","name":"Yang Chi"},"message":"Allow a AsyncSocket to be corked the whole time\n\nSummary: Add a new method to cork a socket in a persistent manner, instead of the current on-off manner. This is default to false. The liger part of turning this on will be in a separate diff.\n\nI thought about whether I need to turn cork off based on some criteria to alleviate the perf degradation. The obvious things I can think off is just amount of data written as a threshold, or a timeout. But TCP is doing this already for us, unless we want the data threshold to be less than MSS, or we want the timeout to be less than 200ms. THoughts?\n\nReviewed By: shikong\n\nDifferential Revision: D2639260\n\nfb-gh-sync-id: 2821f669c9f72d5ac4c33195bb192fc4110ffe9d","distinct":true,"url":"https://api.github.com/repos/facebook/folly/commits/07c150868f7833b8cf659cf888aa3febd8c2ca8a"}]}