DeleteOrderEventArgs Class 
| DeleteOrderEventArgs Class | Table of Content | DateTime Property |
| DeleteOrderEventArgs Properties |
The DeleteOrderEventArgs type exposes the following members.
Properties| Name | Description | |
|---|---|---|
 | BlockSequenceNumber |
Sequence number of message block.
(Inherited from MessageEventArgs<OnixS::ICE::iMpact::MarketData::DeleteOrder>.) |
| DateTime |
Quote entry date time. Milliseconds since Jan 1st, 1970, 00:00:00 GMT.
|
| FeedId |
Feed identifier.
(Inherited from MessageEventArgs<OnixS::ICE::iMpact::MarketData::DeleteOrder>.) |
| IsBundled |
This field is true if messages has been received within bundle (see BundleMarker).
(Inherited from MessageEventArgs<OnixS::ICE::iMpact::MarketData::DeleteOrder>.) |
| Latency |
Processing latency in microseconds.
(Inherited from MessageEventArgs<OnixS::ICE::iMpact::MarketData::DeleteOrder>.) |
| MarketId |
Unique identifier of the market.
|
| NumberOfMessages |
Number of messages in message block.
(Inherited from MessageEventArgs<OnixS::ICE::iMpact::MarketData::DeleteOrder>.) |
| OrderId |
Unique identifier of the order.
|
| ReceivingTime |
Date-time of the message received.
(Inherited from MessageEventArgs<OnixS::ICE::iMpact::MarketData::DeleteOrder>.) |
| RequestTradingEngineReceivedTimestamp |
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.
|
| SentTime |
Date-time of the message sent.
(Inherited from MessageEventArgs<OnixS::ICE::iMpact::MarketData::DeleteOrder>.) |
| 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.
(Inherited from MessageEventArgs<OnixS::ICE::iMpact::MarketData::DeleteOrder>.) |
| SequenceWithinMillis |
Can be used in conjunction with `DateTime` field for priority of
orders within same milliseconds time.
|
| 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.
(Inherited from MessageEventArgs<OnixS::ICE::iMpact::MarketData::DeleteOrder>.) |
See Also