Support Board
Date/Time: Thu, 26 Dec 2024 16:13:17 +0000
Post From: DTC Protobuffer server parsing error
| [2015-12-06 21:26:11] |
| |
|
Yes you got it. And for the last 30 minutes we have been discussing this to determine what is the best protocol for DTC to handle the encoding request. We still have not come to a final decision. Basically the Client and the Server have a default encoding and that needs to be known on each side. When you set the Primary Connection Encoding in Sierra Chart for the DTC Client to Google Protocol Buffers, Sierra Chart assumes the server is using Binary Encoding as the default since all of our own servers use that as the default. Therefore, it sends the encoding request using Binary Encoding. 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 |