Package velox.api.layer1.data
Class ExecutionInfo
java.lang.Object
velox.api.layer1.data.ExecutionInfo
- All Implemented Interfaces:
Serializable
Information about order execution
- See Also:
-
Field Summary
FieldsModifier and TypeFieldDescriptionfinal StringExecution IDfinal booleanIndicates that this exact execution info was already reported to upper layers before, but is being sent to the strategy again because trading data was invalidated.final booleanTrue if execution is simulated by Bookmap.final Stringfinal doublePrice where execution happenedfinal intSize of the executionfinal longTime when execution happened -
Constructor Summary
ConstructorsConstructorDescriptionExecutionInfo(String orderId, int size, double price, String executionId, long time) ExecutionInfo(String orderId, int size, double price, String executionId, long time, boolean isSimulated) ExecutionInfo(ExecutionInfo executionInfo) -
Method Summary
-
Field Details
-
orderId
-
size
public final int sizeSize of the execution -
price
public final double pricePrice where execution happened -
executionId
Execution ID -
time
public final long timeTime when execution happened -
isSimulated
public final boolean isSimulatedTrue if execution is simulated by Bookmap. -
isBuffered
public final boolean isBufferedIndicates that this exact execution info was already reported to upper layers before, but is being sent to the strategy again because trading data was invalidated.
For example, if the selected account changes, all execution infos from the previous account will be reported as disconnected, and the full execution info history for the new account may be replayed. So all such executions will be marked with "isBuffered=true"
Bookmap uses this flag to filter out execution infos that were already reported to upper layers. Therefore, for Data Editors and other Injectable strategies, the value of this flag must remain sane for the execution info received by the strategy, and the corresponding execution info sent back (modified or not) from the strategy to Bookmap. Otherwise, Bookmap's filtering logic may break.
If the strategy modifies an incoming execution info, it should preserve the exact value of this flag, unless it is intentionally creating a new execution info to report to Bookmap. In that case, the flag must be set to false.
A strategy must never change this flag from false to true for incoming execution, and must never set it to true for new data produced by the strategy.- See Also:
-
-
Constructor Details
-
ExecutionInfo
-
ExecutionInfo
-
ExecutionInfo
-
-
Method Details