Support Board
Date/Time: Sun, 29 Dec 2024 01:18:01 +0000
Post From: True Data India Data Feed: Public Offer (Currently Withdrawn)
| [2016-03-04 22:37:33] |
| |
|
A few quick comments regarding this: (1) Are you meaning to say, that you want us to do this connection ourselves ? and that you do not wish to integrate your protocol, in which you are better experienced ?
Yes we are saying that but also take note of the additional information below which explains that the DTC Protocol is not a Sierra Chart specific protocol. Why should we be the ones who do the integration work to your proprietary, complex and undocumented interface which requires additional coding to cross a process boundary? The proper working model is that neither side is integrating to the others service/product and each side uses a common standardized protocol. So you want to us to undertake all the development effort and refer business with no consideration? What have you offered us? We first made you an offer of giving you Sierra Chart free for an extended time. That offer was never accepted and we made a new offer above. We should not even have to provide an offer because your server should have a TCP/IP socket server in it anyway and it should be following a proper protocol like DTC. All of this is very basic and standard. -The DTC protocol is based on FIX. So you have no familiarity with FIX? -So you do not have experience with market data request messages which specify a symbol and a simple flag saying that the client wants to subscribe to data? -What is so hard about that? -So you do not have experience with sending streaming data in a network stream? -So you do not have experience with sending a market data snapshot? -So you do not have experience with data structures? -So you do not have experience with JSON if you decide to use that encoding? -So you do not have experience with the widely used Google protocol buffer encoding if you decide to use that encoding? -So you do not have experience with TCP/IP socket connections? All of this is very very basic, nonproprietary in any way, highly standardized, and thoroughly documented in all of the appropriate places. None of this is Sierra Chart specific in any way. All of this is proven and it works. The DTC Protocol is not a Sierra Chart protocol. It closely follows the FIX protocol where appropriate and uses completely standardized encoding methods. Read over the DTC Protocol page: https://dtcprotocol.org/ And you will understand the basis of all of our statements. ---- We hope we are making our point here. This is not meant to be critical of True Data but to be critical of what is wrong in this industry. The technical practices and attitudes must change. We have been hurt quite badly in the past by using highly proprietary improperly designed executable based methods of integration. This is exactly what True Data is offering. We make no apologies to call it for what it is which is a poor design and promoting substandard practices. There are better methods. We explain this in our Proposal: http://www.sierrachart.com/index.php?page=doc/helpdetails76.html#Proposal Another sad part of all of this is that we had the True Data logo on the DTC Protocol page for about for more than 8 months now because of the clear statements they were going to be implementing support for the protocol, and now they are claiming they did not even understand this. Unbelievable. 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: 2016-03-05 04:36:17
|