{"push_id":884866490,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"38df9aa9963cc73d50efc62c6fd24ce7b6be5820","before":"73ce3219026f4ad15625b8d49dd8b2a71e4624e5","commits":[{"sha":"38df9aa9963cc73d50efc62c6fd24ce7b6be5820","author":{"email":"be235e35a6c144329e4aa1b0fbe2c3f8c71f3676@chromium.org","name":"sadrul"},"message":"mus: Queue events until an ack comes back for previously sent event.\n\nIf an event comes in before the ack for a previously sent event arrives, then\nqueue the event. Once the ack comes back for the previous event, dispatch the\nqueued event as usual (i.e. the targeting happens after the ack comes back).\n\nSome notes:\n. There is a limit to how long mus will wait for the event to be acked. It\n  currently waits 100ms, but we will want different timeouts for the different\n  types of events (e.g. touch events should have smaller timeouts).\n. If the ack does not arrive within the timeout period, then the next queued\n  event (if any) is dispatched anyway. We would want to change this though, e.g.\n  penalize the client, and if a client misses the timeout too often, stop\n  sending it events.\n. Queued events are currently not coalesced.\n\nBUG=533161\n\nReview URL: https://codereview.chromium.org/1480083002\n\nCr-Commit-Position: refs/heads/master@{#362305}","distinct":true,"url":"https://api.github.com/repos/dstockwell/chromium/commits/38df9aa9963cc73d50efc62c6fd24ce7b6be5820"}]}