Support Board
Date/Time: Sun, 19 Jan 2025 17:57:01 +0000
Post From: DTC Protocol Encoding Question
| [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
|