Date/Time: Wed, 27 May 2020 12:47:02 +0000
Post From: Technical Help for Rithmic is Now Discontinued as of December 1, 2019.
|user01283102 - Posts: 142 | Ending Date: 2021-02-24|
And in regards to Rithmic, this is nothing new. This has been an issue for years. And it relates in part to the method of integration Sierra Chart has to Rithmic and this is something that we have talked about here in regards to in process API components which Rithmic uses:
Out of curiousity: Rithmic said they built their Protocol Buffer based API, "R|Protocol" which requires no external process or in-process API component, just for you, at Sierra Chart's request.
They were then perplexed to report that then you do not utilize it. I've used it, and it seems reasonable. I've found one minor bug, nothing major, and when I reported it they fixed it a few days later. Are there other issues, say with the design? Why not just use the Rithmic protocol-buffers API? To be fair, I suppose you could turn it around and ask them why they don't just implement DTC protocol, which is already protocol buffers.
I guess my main concern about the SC Data/Barchart Service in comparison to Rithmic is that Barchart has poor (or at least unknown and no guarantee of precision) clock synchronization method, whereas Rithmic uses PTP/GPS synched clocks to stamp their data, and provides all three relevant time stamps, down to nanoseconds.
Date Time Of Last Edit: 2019-10-25 08:25:46