Sportradar. |
Classes| Class | Description | |
|---|---|---|
 | AliveCheckData | |
| BetOutcome | Localized bet outcome / odds field. |
| BetTypeKey | Bet type key (e.g. "3w" = 2) |
| BetValue | Value associated with a specified BetTypeKey. This includes localized bet type name (e.g. en="hc", fi="Taaoitus") and localized outcomes/odds fields (e.g. "1", "x", "2" in different languages) |
| CipherSettings | |
| ClientPersistentStateItem | Client persistent state item. |
| CommonLoggerManager | |
| ConfigItem | |
| ConnectionData | |
| DynamicConfigIgnoreClassAttribute | Attribute specifying that ConfigurationElement can be ignored by the dynamic configuration handling code. |
| DynamicConfigItemAttribute | Attribute specifying configuration property as dynamic. Dynamic configuration properties can be updated by configuration server in runtime. |
| EntityBase | Serves as a base class for all client data contracts/entities. |
| GlobalSettings | |
| LiveOddsPersistentStateItem | |
| LocalizedString | Localized string container where a string is represented by its international value and a collection of translations to other languages. |
| LoggerData | |
| PersistentStateItem | |
| PersistentStateItemKey | |
| PoisonQueueElt | |
| Priority | Event priority. |
| PriorityQueueElt | |
| ProtocolData | |
| ProtocolProviderType | Type of protocol provider |
| SchemaValidationStrictness |
Schema validation strictness.
Remarks
Order is important - from least to most strict.
Best choice is probably STRICT.
This means it will not spend lots of CPU time while processing eventual junk messages.
Our schema supports any attributes so this is not a problem.
The only issue could present new (unknown) XML elements.
|
| TimeKeeper | |
| TimeKeeperResponse | |
| TypeValueTuple | TypeValueTuple |