Enum SchemaValidationStrictness

Namespace

Sportradar.LiveData.Sdk.Common.Enums

Assembly

Sportradar.LiveData.Sdk.dll

Schema validation strictness. 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.

public enum SchemaValidationStrictness

Fields

OFF = 0

No schema validation is performed at all.

ON = 1

If schema validation fails the message is still deserialized (but it might fail with an exception later).

STRICT = 2

Schema validation failure means the message must be discarded immediately.

VERY_STRICT = 3

Same as above except that any warning is also treated as fatal error.