MessageEventArgs
| MessageEventArgs | Table of Content | BlockSequenceNumber Property |
| MessageEventArgs<OnixS::ICE::iMpact::MarketData::NewOptionsMarketDefinition> Properties |
The MessageEventArgs<OnixS::ICE::iMpact::MarketData::NewOptionsMarketDefinition> type exposes the following members.
Properties| Name | Description | |
|---|---|---|
 | BlockSequenceNumber |
Sequence number of message block.
|
| FeedId |
Feed identifier.
|
| IsBundled |
This field is true if messages has been received within bundle (see BundleMarker).
|
| Latency |
Processing latency in microseconds.
|
| NumberOfMessages |
Number of messages in message block.
|
| ReceivingTime |
Date-time of the message received.
|
| SentTime |
Date-time of the message sent.
|
| SequenceNumber |
Each message is assigned a sequence number that increases monotonically on the server side. To save
bandwidth, the sequence number is a field in the block header, instead of every message. The sequence number
for the first message is used in the header, and the client is expected to derive the sequence numbers for
subsequent messages in the block. In the case of a heartbeat which includes only header in the block, the
expected next sequence number is used.
|
| SessionNumber |
The session number is used so that a client can easily detect when a new session has started after the daily
maintenance window or failure on the server side. It should stay the same for a given multicast channel until a
new session has started. It should be noted that the same number can be used by different multicast channels.
|
See Also