{"push_id":922780187,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"29136a018694b23d838f23afd852530cd3527bf0","before":"23abc425d4b63005adf224ab975f6904fa693040","commits":[{"sha":"33dcec7b748aee42518586c78656e060cc584412","author":{"email":"db043b2055cb3a47b2eb0b5aebf4e114a8c24a5a@centricular.com","name":"Sebastian Dröge"},"message":"netclientclock: Only ever run one clock against a specific server\n\nIf multiple net/NTP clocks are created for the same server, reuse the same\ninternal clock for all of them. This makes sure that we don't flood the server\nwith too many requests and also possibly allows faster synchronization if\nthere already was an earlier synchronized clock when creating a new one.","distinct":true,"url":"https://api.github.com/repos/StreamUtils/gstreamer/commits/33dcec7b748aee42518586c78656e060cc584412"},{"sha":"29136a018694b23d838f23afd852530cd3527bf0","author":{"email":"db043b2055cb3a47b2eb0b5aebf4e114a8c24a5a@centricular.com","name":"Sebastian Dröge"},"message":"netclientclock: Destroy a cached clock 60 seconds after its last use\n\nThere's not much lost by having the clock idle around a bit longer but it will\npotentially allow anybody wanting to use the same clock server again to sync\nmuch faster.","distinct":true,"url":"https://api.github.com/repos/StreamUtils/gstreamer/commits/29136a018694b23d838f23afd852530cd3527bf0"}]}