Login Page - Create Account

Support Board


Date/Time: Sun, 19 May 2024 15:33:04 +0000



Post From: CQG Data Incorrect

[2018-05-09 18:58:25]
Sierra Chart Engineering - Posts: 104368
Message sent to CQG:
We require that your protocol definition file compiles under Google protocol buffer version 3.

We have to use Google protocol buffer version 3 compiler and library because we use other Google protocol buffer implementations which require that.

The protocol definition file you linked to here does not compile under Google protocol buffer version 3 compiler.

You do not have to on your server itself support Google protocol buffer version 3. You just need to have another version of your protocol definition file which will compile under version 3. It still will be the same but just some minor changes are needed.

As long as the overall structure of the messages is the same, the underlying encoding will remain the same. We know that from experience and that is what is documented in the Google protocol buffer documentation. So it is not a problem to provide support for version 3. The underlying encoding will be the same.

This is important for us because we are using an older CQG Web API definition file and we are wondering if this is what is leading to missing data for our users with the real-time market data. We have many reports of that.

Now is this really going to get what we want, we doubt it very much. This is why we just simply are helpless, in this regard and this is why we have to focus on things that are productive.

And eventually get to a point where CQG can be completely eliminated.
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