Support Board

Date/Time: Fri, 26 Apr 2024 08:44:58 +0000

Post From: Notice: Transact Websocket Connectivity Issue

[2019-08-23 16:01:25] Link To Thread - Link To Post [Go To First Post]
Sierra Chart Engineering - Posts: 104368
In regards to market data feed issues with Transact, we have discussed this now with Transact. They are setting up a test server to better analyze this, and we will use their JSON encoding method rather than binary. They say that would be more bandwidth efficient. But the binary method is what the old bridge program uses anyway. It certainly is faster on the decoding/client side. And also, we see no evidence this issue is on the Sierra Chart side. There is some framing problem which clearly looks like on their side. For example we see errors indicating extension bits set, and invalid opcodes. We never see these with any other service which uses a websocket connection. This would indicate a problem with the actual data coming from the remote side. And we have analyzed the Sierra Chart websocket functionality, and that is according to specifications. 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: 2019-08-23 21:54:49