Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Sat, 18 May 2024 05:59:56 +0000
Post From: Server Side OCO Failure, and Incorrect Position/Missing Fill Data after Connection Reset
| [2016-10-21 04:04:52] |
| |
|
This further only strengthens the need for a common communication protocol which is the DTC protocol: https://dtcprotocol.org Or the FIX protocol. And we cannot even quickly resolve this problem either. We plan to do some more work with the Rithmic API, in about a couple of weeks but is not something we can just simply resolve immediately at this moment in time. These external API components are nothing but trouble: https://www.sierrachart.com/index.php?page=doc/helpdetails76.php The intention of sending the message to Rithmic is so that the brokers can get a credit for what they were paying for. And once again we want to point out that the Sierra Chart order confirmations always made it very clear that OCO orders were not supported on the server side when submitting the order. This is why it is important to pay attention to those confirmations. All these months no one ever brought this to our attention that the order confirmation was in conflict with the setting to use server-side OCO orders with Rithmic. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2016-10-21 04:08:26
|