Thanks for summarizing, Alexander. I still think that your suggested roadmap is too complex. Effectively, every time JBT makes a trade, according to your roadmap, there would be 3 orders (first one canceling the previous stop, second one is submitting the primary order, and the third one is a new stop order). Managing these three orders, which can trigger at any time, is not trivial. For example, it's entirely possible that before you have a chance to cancel the previous stop, it triggers. The "cancel" request will therefore be never executed, which needs to be handled correctly by JBT. The opposite can happen, as well. In these scenarios, you may end up with either "phantom orders", or duplicate orders. I am not saying that sound order management can't be done, but again, it's not trivial.
I'll keep thinking about adding stops to JBT, but one thing that I would point out is that if you have a reliable network connection (let's say on a dedicated hosted server), or a backup network connection on your own server, none of these complicated order placement logistics would be necessary. -- You received this message because you are subscribed to the Google Groups "JBookTrader" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/jbooktrader?hl=en.
