Support Board
Date/Time: Sun, 19 Jan 2025 17:44:34 +0000
[Programming Help] - DTC Protocol Encoding Question
View Count: 1111
| [2018-04-22 20:53:57] |
| User942837 - Posts: 108 |
|
Hi, I am using Google protocol buffers in my implementation but I am trying to have a Sierra Chart client as well Connected to the same server so I decided to change the Encoding to Automated. Login seems to be working fine as I receive a LoginResponse Message back on automated encoding but I am receiving an error on google protocol buffer deserialisation. This is what sierrachart is reporting in message log. DTC client #45. <REMOVEDIP> | Sent Logon response with error to client. Username: <REMOVED> <REMOVED>8ZSample. Result text: DTC protocol version 168953864 is unsupported | 2018-04-22 20:37:50 The byte array I am receiving for LogonResponse is 256 byte array (252 for the protobuf message). When I switch the Encoding on the server to Google Protocol Buffers, the length of the message I am getting is 110 bytes (106 for the protobuf) message. (which is the correct size). To me this seems there is something that is working differently on the way you are framing the messages when encoding is automatic. My code works fine if I set the Encoding to Google Protocol Buffers. If my code is working fine on Google Protocol Buffer setting, I would expect to work the same on automated especially if you are recognising the login request and sending a response. Can you kindly look into this please? Date Time Of Last Edit: 2018-04-22 20:54:38
|
| [2018-04-22 21:16:34] |
| |
|
The problem is on your side. Do not ever claim a "Bug" in the subject line because that is not the case and has never been the case either. Refer to the documentation here: DTC Messages and Procedures: Encoding Request Sequence but I am trying to have a Sierra Chart client as well Connected to the same server so I decided to change the Encoding to Automated. When Sierra Chart is connecting to the DTC Protocol server in another instance of Sierra Chart, it does not matter how the "Encoding" is set because it is automatically negotiated according to the DTC Protocol.
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: 2018-04-22 21:17:14
|
| [2018-04-22 21:35:56] |
| User942837 - Posts: 108 |
|
yes correct. Sorry about this. Sierra Client did manage to connect when encoding is set to Google protocol buffers. I missed this. I didn't know that I had to send an encoding request for Automated to work properly. Apologies for this. |
To post a message in this thread, you need to log in with your Sierra Chart account: