Login Page - Create Account

Support Board


Date/Time: Mon, 20 May 2024 15:25:02 +0000



Post From: Regarding Rithmic

[2018-10-14 23:52:55]
Sierra Chart Engineering - Posts: 104368
Also it really is very clear Rithmic can solve this issue from their side. And they should.

And we do not know whether this new bridge program is going to be stable or not. It would have been very irresponsible for us in the past to have released it but we are now and we do not even know what the consequence of it is going to be. It could be fine but in our judgment, it should not be trusted. But to what extent it is going to cause a problem we do not know.

For example we would never release our main program Sierra Chart with such a problem. We would determine the problem and resolve it. But this situation is unresolvable by us because we do not control the source code and because the whole concept of using an API component is ridiculous to begin with. We explain this in help topic 76:
Sierra Chart Does not Support External Service API Components


And when our users wonder why periodically we put Rithmic down it is because of this reason. Look at the trouble you are facing with Rithmic connectivity. We are only being proven right here. And for anyone to put blame or responsibility on us is completely out of bounds.



So at this point, we recommend strongly for Rithmic to take the necessary steps on their side to support the connection details we are currently using. There should be no trouble with this. And then they need to get the new websocket and Google protocol buffer API out which bypasses this client-side component.
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-10-15 00:16:54