Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Sun, 28 Apr 2024 20:20:17 +0000
Post From: CQG Web API: Server-Side OCO
| [2018-10-09 18:00:38] |
| User882915 - Posts: 32 |
|
Thank you for your reply and the link. While that page indeed clarified a few things, regarding my main concern (whether my OCOs will be handled server-side with full cancelling functionality, once a parent order has been filled, even if I then lose my internet connection), I'm still confused: Answering my question No. 3 you write that this is most likely coincidental and that I might have updated Sierra Chart. Yes, I update it on each weekend (if there is a new version); now I'm on version 1815 (64 bit) and that was the 2nd update since my trade where "Server Side OCO order" still appeared. I did not see any notification about a version 1819 (or is there different update numbering for 32 and 64 bit versions)? (Note that I do not download "PreReleases".) But if it was caused by the update, actually YOU should be able to tell me if in the current version the type of messaging in the trade activity log was changed by Sierra chart or not, right? Moreover, on the page you sent me the link of, the following is written: How do you know whether your Trading service supports OCO functionality? ... You will know if your Trading service supports OCO functionality when you submit an order. In the Trade Activity Log, in the Order Action Source field for the order, server-side managed OCO orders will contain the text Server side OCO order.
As I explained in my first message, that "Server Side OCO Order" indication had disappeared and was replaced by "Client Managed Bracket Order". So, does that now mean that my OCOs are NOT handled server side, in spite of the clear indication on your Data and Trading Services page for CQG that Server-Side OCOs ARE supported in both, FIX and Web API? Or has the text on the page not been updated after Sierra Chart had changed the description in the trade activity log in one of the last updates? As far as I understand the entire page, currently I tend to believe that my OCOs are NOT handled server-side once the parent order got filled, as it is not indicated in the trade activity log. The question is WHY? (I am using Web API, which should support it, and I have "Use Server Side OCO Orders" ticked under "General Trade Settings", too.) Unfortunately, I don't understand your following sentence: We also need to look at the logging indicating whether OCO and bracket orders are managed on the client-side or server-side. We can see how when a bracket is client managed, there still can be server-side OCO and that needs to be indicated.
I sent you the logging as attachments. Or are you talking about some other logging? If so, which? Please let me know, and I can send it to you. Or did you mean that you will look at my logging from your side and come back to me on that one? Thank you very much in advance for your feedback. |