forwardMarketEventArgs Class   Table of ContentDateTime Property forward
MarketEventArgs Properties

The MarketEventArgs type exposes the following members.

Properties
  NameDescription
Public propertyBlockSequenceNumber
Sequence number of message block.
(Inherited from MessageEventArgs<OnixS::ICE::iMpact::MarketData::MarketEvent>.)
Public propertyDateTime
Date time this message was sent. Milliseconds since Jan 1st, 1970, 00:00:00 GMT.
Public propertyEventType
Market event type.
Public propertyFeedId
Feed identifier.
(Inherited from MessageEventArgs<OnixS::ICE::iMpact::MarketData::MarketEvent>.)
Public propertyIsBundled
This field is true if messages has been received within bundle (see BundleMarker).
(Inherited from MessageEventArgs<OnixS::ICE::iMpact::MarketData::MarketEvent>.)
Public propertyLatency
Processing latency in microseconds.
(Inherited from MessageEventArgs<OnixS::ICE::iMpact::MarketData::MarketEvent>.)
Public propertyMarketId
Unique identifier of the market.
Public propertyNumberOfMessages
Number of messages in message block.
(Inherited from MessageEventArgs<OnixS::ICE::iMpact::MarketData::MarketEvent>.)
Public propertyReceivingTime
Date-time of the message received.
(Inherited from MessageEventArgs<OnixS::ICE::iMpact::MarketData::MarketEvent>.)
Public propertySentTime
Date-time of the message sent.
(Inherited from MessageEventArgs<OnixS::ICE::iMpact::MarketData::MarketEvent>.)
Public propertySequenceNumber
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.
(Inherited from MessageEventArgs<OnixS::ICE::iMpact::MarketData::MarketEvent>.)
Public propertySessionNumber
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.
(Inherited from MessageEventArgs<OnixS::ICE::iMpact::MarketData::MarketEvent>.)
Top
See Also