Login Page - Create Account

DTC Protocol Discussion Forum


Date/Time: Mon, 28 Nov 2022 01:22:27 +0000


DTCMessageType : differences between binary encoding vs protocol buffers

View Count: 1086

[2021-06-11 03:34:45]
homestar - Posts: 21
In DTC version 8, I've noticed two differences in message type integers between DTCProtocol.h (the fixed-length binary encoding) and DTCProtocol.proto (protocol buffers). They are:

- In the .h file, we have HISTORICAL_ACCOUNT_BALANCE_RESPONSE==606. In the .proto file, we have HISTORICAL_ACCOUNT_BALANCE_RESPONSE==605.
- In the .h file, we have MARKET_DATA_UPDATE_BID_ASK_FLOAT_WITH_MILLISECONDS==144. In the .proto file, there is no such enum member defined.
[2021-07-23 07:56:31]
DTC Engineering - Posts: 320
We apologize for the delay.

This is being corrected:
- In the .h file, we have HISTORICAL_ACCOUNT_BALANCE_RESPONSE==606. In the .proto file, we have HISTORICAL_ACCOUNT_BALANCE_RESPONSE==605.

We are adding this:
- In the .h file, we have MARKET_DATA_UPDATE_BID_ASK_FLOAT_WITH_MILLISECONDS==144. In the .proto file, there is no such enum member defined.

This will be out in the next Sierra Chart release later today.

To post a message in this thread, you need to log in with your Sierra Chart account:

Login

Login Page - Create Account