Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Fri, 19 Apr 2024 19:43:39 +0000
Post From: Notice: Transact Websocket Connectivity Issue
| [2019-08-24 06:00:04] |
| |
|
We also want to say that this is very easily resolved by Transact and we told them this as well. They just need to reduce the size of the websocket frames. Clearly there is some corruption occurring when they are too large. What the maximum size should be, we do not know but we suggested 4K. That will at least immediately mitigate the problem. At least we think so. This is just based on a reasonable assumption. We see no evidence at all that the frames are mishandled on the Sierra Chart side and our websocket processor has been in extensive use for years now with 0% problems like this with CQG and other services. If there is some problem on our side, it must have something to do with the large frame side but as we said, we went over this again today and saw no issue even when the frame size approaches 4 GB. All of the network I/O, and decryption, and websocket frame handling, is all common code which is extensively used every day by other services by thousands of users with no trouble. 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-25 05:41:37
|