OnExecutionUpdate()? Executions do not get updated!

[koganam]

That makes no semantic sense. Orders are updated; so are positions, so OnOrderUpdate() and OnPositionUpdate() make sense. Executions occur; they are never updated. Once an execution occurs, it is done.

That being said, I am sure it may be too late to make a change back to OnExecution(). Hey, I am just saying.

[NinjaTrader_Matthew]

Internally, from the adapter/connection, there are 3 operations on an Execution: Add/Remove/Update (e.g, Add operation, we have to pair an order object to an execution). We expose the Update operation to NS as this is relevant to an end user.

The name is accurate internally and since we're now giving you guys the actual internal events, the name makes sense from that perspective.

[koganam]

Internally, from the adapter/connection, there are 3 operations on an Execution: Add/Remove/Update (e.g, Add operation, we have to pair an order object to an execution). We expose the Update operation to NS as this is relevant to an end user.

The name is accurate internally and since we're now giving you guys the actual internal events, the name makes sense from that perspective.

Thanks for the response. Your argument makes sense from a development perspective.