I have a few questions for you. Historical data is important to many traders, not all, but many. Perhaps, the most universal way to deal with it would be a data feed simulator. Such a tool would guarantee a seamless access to a local or centralized data of whatever format. To me, for example, having fed into NT the 1min CSI database (both in real time for replay and as a historical) would prove invaluable. Some people have a lot of tick text files, and so forth. So, this data feed simulator would sit at, say, 7497, local or remote, and emulate IB feed using historical data as a source.
In case of a text file(s) it should be possible to define a format dynamically (some preprocessing probably is necessary, like indexing for the faster access), CSI and other dbs interface would be predefined etc. Of course, somewhat bigger subset of provider’s API needs to be simulated, as compared to a simple bid/ask/trade. This simulator will interact with any charting software, not only NT, but who's counting.
It would be nice to have a centralized repository where NT users would contribute their data for further free and unlimited usage by the others, but that, I guess, will eat up the entire www bandwidth. Yet, the net community does have a way of figuring stuff out - when people are really interested.
Anyway, it is no big deal to code something like this, at least a working alpha. I would do that and then make it public and free, of course.
I don’t want, however, to be inventing a bicycle. Maybe such a feed exists already? Or NT 7 will support it in some other way? The external data feed in NT6.5 is different from what I want, as far as I can see.
If you are at liberty to say, please, do.
Also, would you be willing to help? What data feed is better (easier, or richer, or otherwise) to simulate? APIs are well documented, but from NT standpoint? What API subset exactly NT needs from data feed to support historical data retrieval and real time acquisition? Maybe there is something else I need to know?
Best,
jbarr

). AFAIK Ask/Bid is for real-time data, and playback is not good for charting/testing.
Comment