DTC Protocol Discussion Forum

Date/Time: Fri, 29 Nov 2024 15:36:14 +0000

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

[2020-10-25 01:08:56] Link To Thread - Link To Post [Go To First Post]
vp_ftw - Posts: 12
That is what the docs state, but I'm not seeing one. I've verified bytes and message type byte order (LittleEndian) over the wire with wireshark and I can't see anything potentially wrong with my requests. Is there a test case that proves these request/response flows are operational with protocol buffers? I find it interesting that I didn't receive heartbeats from the server on SCv2177 but began to receive them after updating to v2182. If protocol buffers aren't 100% complete and tested within the SC sever I'm happy to help there however I can. 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 Hoping we can get this figured out. To illustrate my efforts on this side: DEBUG [2020-10-24 19:17:13.100] accountData.go:28 Sending TRADE_ACCOUNTS_REQUEST TRACE [2020-10-24 19:17:13.100] connection.go:260 Packed message with TypeID: 400 with length(6) and contents: (0x060090010801) Expanding: 0x060090010801 // LittleEndian Message Length as uint16 06 00 // LittleEndian Message Type ID as uint16 90 01 // bigEndian 0x0190 == 400 == TRADE_ACCOUNTS_REQUEST // 2 bytes of protopuf data 08 01