Click or drag to resize

ILiveScout Events

The ILiveScout type exposes the following members.

Events
 NameDescription
Public eventOnClosed Signals that the underlaying connection has been closed (disconnect)
Public eventOnFeedError Signals that a feed error has occurred (e.g. we got disconnected from the feed server, XML message parsing error occurred).
(Inherited from ILiveFeeds)
Public eventOnLineups Player lineups for both teams were received.
Public eventOnMatchBookingReply Reply sent when a client books a match. If match booking failed for some reason (match already bought, match finished etc.), the reply will contain additional explanation.
Public eventOnMatchData Occurs when [on match data].
Public eventOnMatchList Signals that a list of matches in the time frame requested by the client has been received.
Public eventOnMatchListUpdate Signals that an unsolicited list of matches has been received.
Public eventOnMatchStop Reply sent after client unsubscribed from a match. It could also be sent if match subscription failed for any reason (e.g. too many match subscriptions).
Public eventOnMatchUpdate

Signals that a match update message was received. There are three types of match information messages: full match feed, delta match feed and delta update feed (see MatchHeader.TypeOfFeed). 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).

Public eventOnMatchUpdateDelta Delta match update event. See OnMatchUpdate for more info.
Public eventOnMatchUpdateDeltaUpdate Delta update match update event. See OnMatchUpdate for more info.
Public eventOnMatchUpdateFull Full match update event. See OnMatchUpdate for more info.
Public eventOnOpened Signals that the underlaying connection has been opened (connect)
Public eventOnScoutInfo Signals some basic information about the match. Sent out when a client subscribes to a match.
Top
See Also