Interface LiveScoutFeedListener


  • public interface LiveScoutFeedListener
    Represents a listener used to observe LiveScoutFeed implementations
    • Method Detail

      • onInitialized

        void onInitialized​(LiveScoutFeed sender)
        Invoked when the feed is initialized and you can accept bets. It is invoked exactly once after the feed has been opened.
        Parameters:
        sender - - originating feed
      • onOpened

        void onOpened​(LiveScoutFeed sender)
        Invoked when the feed is opened.
        Parameters:
        sender - The LiveScoutFeed sender of the event.
      • onFeedEvent

        void onFeedEvent​(LiveScoutFeed sender,
                         FeedEventType eventType)
        Invoked by the observed live feed when it encounters an special event related to the behavior of the server.
        Parameters:
        sender - The LiveScoutFeed sender of the event.
        eventType - The FeedEventType member specifying the type of the occurred event.
      • onLineupsReceived

        void onLineupsReceived​(LiveScoutFeed sender,
                               LineupsEntity lineups)
        Invoked by the observed LiveScoutFeed when player lineups for both teams are received.

        The event is dispatched immediately after subscribing to a match and every time the lineup changes. XML configuration option "Send lineups for matches where this is available" needs to be activated (currently works just for deep coverage soccer matches).

        Parameters:
        sender - The LiveScoutFeed sender of the event.
        lineups - The LineupsEntity representing the received lineups.
      • onMatchBooked

        void onMatchBooked​(LiveScoutFeed sender,
                           MatchBookingEntity matchBooked)
        Invoked by the observed LiveScoutFeed when a match-booked reply is received. Reply is sent by the live-scout server when a client books a match. If match booking failed for some reason (match already booked, match finished etc.), the reply will contain additional explanation.
        Parameters:
        sender - The LiveScoutFeed sender of the event.
        matchBooked - The MatchBookingEntity representing the received message.
      • onMatchUpdateReceived

        void onMatchUpdateReceived​(LiveScoutFeed sender,
                                   MatchUpdateEntity matchUpdate)
        Invoked by the observed LiveScoutFeed when match update message is received. There are three types of match information messages: full match feed, delta match feed and delta update feed (see ScoutFeedType. All three can contain statistical information as well as individual events (an event being a goal, card, etc.).

        When a client application subscribes to a match, it will receive a full match update immediately after (given the subscription was successful). This message will contain all data for the match. Different event types are offered for different sports. Note that new event types will be added in the future.

        After a full match update is received, most updates will be sent as delta updates. In these messages only the new data is sent, if a yellow card is given only this event will be sent. In addition summary data will be sent for the event type in question, i.e. the total number of yellow cards for the home/away team for the match.

        If an existing event is changed, a delta update is sent for this event. E.g. a yellow card event is entered, and 1 minute later the event is updated by including which player got the card. Client must consider this as an update to an existing event, and not a new event (based on Event Id property).

        Parameters:
        sender - The LiveScoutFeed sender of the event.
        matchUpdate - The MatchUpdateEntity representing the received match-update message
      • onClosed

        void onClosed​(LiveScoutFeed sender)
        Invoked when the feed is closed.
        Parameters:
        sender - The LiveScoutFeed sender of the event.