Support Board
Date/Time: Wed, 27 Nov 2024 22:51:25 +0000
Post From: Work-around for server side OCO's
| [2014-04-06 19:27:02] |
| User92763 - Posts: 14 |
|
I'm curious if there would be a way to program a work-around for servers that don't support OCO orders. As an example: Say that you have placed a parent order with attached orders (10T stop and 20T target), as the server does not support OCO orders, the orders are handled locally in SC. At the same time that the parent order fills, an opposing order for a stop is sent that is not an OCO that will be accepted and reside on the server side (lets call this a catastrophic stop... set at 30T). The OCO orders continue to work locally, and if either target or stop is hit the OCO group cancels the opposing order, but in addition sends a cancel order for the catastrophic stop residing on the server. In this way, if you should experience an internet service interruption, at least you have that catastrophic order on the server. Of course the obvious solution would be to use a server that supports OCO's, but you are limited to the number of brokers that you can choose from. I don't know that such a thing would be popular enough to incorporate it as part of the SC platform, but if it could be programmed as described, I may be willing to pay for programming costs, and make use of it myself. I haven't considered all the possible downside scenarios yet... just asking if it's possible. Thanks. |