{"push_id":720337468,"size":1,"distinct_size":1,"ref":"refs/heads/0.5.x","head":"87367ac29d69edf3edc9ab16ec80bb0d242cede8","before":"2e32865ec6c0681bcfeebf1af92accb799bd5206","commits":[{"sha":"87367ac29d69edf3edc9ab16ec80bb0d242cede8","author":{"email":"170d84963e98e44aa9c5756a5ca97e3ce2dff8ab@netflix.com","name":"Nitesh Kant"},"message":"Adding a facility to emit custom events on EventListener.\n\nCurrently protocol specific listeners only provide pre-defined events. In cases, when someone is building a custom protocol over an existing protocol (TCP, HTTP), there would be a need of custom events that can be tapped for metrics, feedback to `ConnectionProvider`s etc.\n\nThis change adds 4 variants of `onCustomEvent` methods to `EventListener` (Common class for all listeners) with an ability to emit a custom event with duration and error. The intent of these overloads is that it will allow the actual event class to be a constant (to avoid object allocation overhead) for common usecases of emitting events with duration and error.\n\nRxNetty would not emit any events as custom, it will always be emitted by user code.","distinct":true,"url":"https://api.github.com/repos/NiteshKant/RxNetty/commits/87367ac29d69edf3edc9ab16ec80bb0d242cede8"}]}