forwardDeleteOrderEventArgs Class   Table of ContentDateTime Property forward
DeleteOrderEventArgs Properties

The DeleteOrderEventArgs type exposes the following members.

Properties
  NameDescription
Public propertyBlockSequenceNumber
Sequence number of message block.
(Inherited from MessageEventArgs<OnixS::ICE::iMpact::MarketData::DeleteOrder>.)
Public propertyDateTime
Quote entry date time.
Public propertyFeedId
Feed ID.
(Inherited from MessageEventArgs<OnixS::ICE::iMpact::MarketData::DeleteOrder>.)
Public propertyIsBundled
Bundle marker. This field is true if messages has been received within bundle (see DeleteOrder).
(Inherited from MessageEventArgs<OnixS::ICE::iMpact::MarketData::DeleteOrder>.)
Public propertyLatency
Processing latency in microseconds.
(Inherited from MessageEventArgs<OnixS::ICE::iMpact::MarketData::DeleteOrder>.)
Public propertyMarketId
Unique identifier of a market.
Public propertyNumberOfMessages
Number of messages in message block.
(Inherited from MessageEventArgs<OnixS::ICE::iMpact::MarketData::DeleteOrder>.)
Public propertyOrderId
Unique identifier of the order.
Public propertyReceivingTime
Time when the UDP packet was received by Handler.
(Inherited from MessageEventArgs<OnixS::ICE::iMpact::MarketData::DeleteOrder>.)
Public propertyRequestTradingEngineReceivedTimestamp
This field can be used to get the time the trading engine received the request that triggers this message. The format is nanoseconds since Jan 1st, 1970, 00:00:00 GMT. The nanosecond part is currently 000 and might be supported later. Note: This field could be set to different values or 0 for some scenarios. Please refer to the FAQs for more details.
Public propertySentTime
DateTime object created using number of milliseconds since Jan 1st, 1970, 00:00:00 GMT.
(Inherited from MessageEventArgs<OnixS::ICE::iMpact::MarketData::DeleteOrder>.)
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::DeleteOrder>.)
Public propertySequenceWithinMillis
Can be used in conjunction with DateTime field for priority of orders within same milliseconds time.
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::DeleteOrder>.)
Top
See Also