Posted: May 05, 2011 @ 03:47 AM             Msg. 1 of 2

Imagine the following initialization and trading:

oecClient.OnOrderStateChanged += new OnOrderStateChangedEvent(oecClient_OnOrderStateChanged);

...
later
...

order = oecClient.SendOrder(orderDraft)


After sending an order the event OnOrderStateChanged is fired more times with the state Sent. The first time it occures before oecClient.SendOrder(orderDraft) returns an order (this time the order's ID is not set) and then there is thesecond occurence. This looks reasonably. But there are also another occurences of the fired event with the state Sent.


From the documentation for the OrderState Enumeration we can see the following:

Basic state diagram for order lifetime.

Sent -> [Held] -> Working -> Completed.
\-> Rejected. \-> Cancelled.


I would expect that Sent stat will occur only once (perhaps twice). Whay are there multiple occurences ? Additionaly, the Sent state is marked as obsolete. Which state is intended to be used instead of Sent in the future ?

---

Alastair Cunningham

Posted: May 25, 2011 @ 11:33 AM             Msg. 2 of 2

Hello,

Diagram shows possible transitions from one state to another.

Unfortunately, Sent status can be fired more than once.

Sent status is not obsolete.

---

Victor Vins
Software Developer