Marathon must receive a response code in the 200's or it assumes the callback is not responding. In order to get around this and allow for future event types, the events/ API resource should take any request as long as it has the following:
timestamp
eventType
In conjunction a MarathonEvents class should be created that wraps the RingBuffer that allows a caller to receive top level information about events without having to retrieve the entire contents of the ring buffer.
Marathon must receive a response code in the 200's or it assumes the callback is not responding. In order to get around this and allow for future event types, the events/ API resource should take any request as long as it has the following:
In conjunction a MarathonEvents class should be created that wraps the RingBuffer that allows a caller to receive top level information about events without having to retrieve the entire contents of the ring buffer.