forwardRfqEventArgs Class   Table of ContentMarketId Property forward
RfqEventArgs Properties

The RfqEventArgs type exposes the following members.

Properties
  NameDescription
Public propertyBlockSequenceNumber
Sequence number of message block.
(Inherited from MessageEventArgs<OnixS::ICE::iMpact::MarketData::Rfq>.)
Public propertyFeedId
Feed ID.
(Inherited from MessageEventArgs<OnixS::ICE::iMpact::MarketData::Rfq>.)
Public propertyIsBundled
Bundle marker. This field is true if messages has been received within bundle (see Rfq).
(Inherited from MessageEventArgs<OnixS::ICE::iMpact::MarketData::Rfq>.)
Public propertyLatency
Processing latency in microseconds.
(Inherited from MessageEventArgs<OnixS::ICE::iMpact::MarketData::Rfq>.)
Public propertyMarketId
Unique identifier of a market.
Public propertyMarketTypeId
Market type ID.
Public propertyMessageTimestamp
Date time of the RFQ.
Public propertyNumberOfMessages
Number of messages in message block.
(Inherited from MessageEventArgs<OnixS::ICE::iMpact::MarketData::Rfq>.)
Public propertyQuantity
Quantity.
Public propertyReceivingTime
Time when the UDP packet was received by Handler.
(Inherited from MessageEventArgs<OnixS::ICE::iMpact::MarketData::Rfq>.)
Public propertyRfqSystemId
System ID of the RFQ.
Public propertySentTime
DateTime object created using number of milliseconds since Jan 1st, 1970, 00:00:00 GMT.
(Inherited from MessageEventArgs<OnixS::ICE::iMpact::MarketData::Rfq>.)
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::Rfq>.)
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::Rfq>.)
Public propertySide
Tells whether request represents bid or offer.
Public propertyUnderlyingMarketId
Underlying market ID.
Top
See Also