DTC Protocol Discussion Forum

Date/Time: Fri, 29 Nov 2024 15:53:04 +0000

Post From: Protocol buffers with golang - no response on wire to TRADE_ACCOUNTS_REQUEST

[2020-11-05 06:02:31] Link To Thread - Link To Post [Go To First Post]
DTC Engineering - Posts: 320
We apologize for the delay with the response. We do not always monitor this board every day. Is there a test case that proves these request/response flows are operational with protocol buffers? This can be verified by connecting Sierra Chart using the DTC Sub Instance service to an instance of Sierra Chart with the DTC Protocol Server enabled. The encoding method needs to be protocol buffers which is not controllable by users but we are able to control that and we did verify this does work. The accounts were sent. But we do see that only the first response is responded to and any additional ones are ignored, if there are no new trade accounts. So we will fix that in the next release. This must be what you are experiencing. I find it interesting that I didn't receive heartbeats from the server on SCv2177 but began to receive them after updating to v2182. We do not know why this would be the case. There has been no change with heartbeats. I definitely prefer the ease of implementation of DTCProtol over FIX or CQG's web api. CQG's web api would also interfere with my human based trading requiring a second data subscription for API use! :P Wow. This is really good to hear. It is good to hear others, say what we definitely know to be true. Date Time Of Last Edit: 2020-11-05 06:05:49