DTC Protocol Discussion Forum
- DTC Protocol Discussion Forum |
- Search Board |
- Control Panel |
- View My Posts / Threads |
- Direct Messages
Date/Time: Fri, 29 Nov 2024 16:33:42 +0000
Post From: Does SC historical connection support Google Protocol Buffers?
| [2017-05-05 22:02:05] |
| Queeq - Posts: 42 |
|
Hi, I am testing DTC protocol with Sierra Chart (version 1549). SC server encoding is set to automatic. Intraday logon sequence goes fine, SC acknowledges the use of Protobuf, and the following requests are flowing successfully. Here's the Encoding Response: b'\x07\x00\x00\x00\x04\x00\x00\x00DTC\x00' ^^^^^^^^ However, when connecting to Historical data port, Encoding Response indicates binary: b'\x07\x00\x00\x00\x00\x00\x00\x00DTC\x00' ^^^^^^^^ Consequently, the login sequence fails. SC itself reports the following in the log: HD Server | Unexpected DTC encoding request: 4 | 2017-05-05 21:41:07 The client program is written in Python and protobuf classes are generated from proto v2 file. Have I missed something? Date Time Of Last Edit: 2017-05-05 22:03:04
|