SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Strategies & Market Trends : Bottom (and Top) Pickers, Unite! -- Ignore unavailable to you. Want to Upgrade?


To: Atin who wrote (139)1/19/2001 3:54:26 PM
From: Michael Watkins  Read Replies (2) | Respond to of 214
 
This makes very little sense (not saying you're wrong, just that it doesn't make sense). QCharts is fed by QFeed

Atin,

Well from your perspective it doesn't make sense, but that's because your application is reliant on the historical data served up by the servers to draw charts.

QFeed itself is more reliable than QCharts, I stand by that since I've been collecting QFeed raw data for eons now. I think you'll get similar responses from Teresa and other Tradestation/Dynastore users.

The primary difference is that Tradestation stores all of its tick / bar data locally. So when I open a chart on a symbol, no request to the server happens to bring back X number of bars of T duration. All that data is local, and being updated tick by tick whether I have a chart open or not. The Tradestation data collector, GlobalServer, of course must be left running, as well as the Dynastore interface to QFeed/GlobalServer.

Qfeed keeps on chugging even though other users on the same server complain that QCharts is not dishing up charts. In fact, I have seen this for myself, if I am on boston-r01 and QCharts on boston-r01 dies, 99% of the time, QFeed is not dead at all.

What isn't reliable is calling up historical bar data in Qcharts. Actually a lot of things aren't reliable in Qcharts ;)

I have assumed that the claims Quote.com makes about Qfeed highly compressing its data stream are probably accurate, but to be honest, I don't really care. It just works.

I capture some 300 symbols in real time, and Qfeed just keeps on ticking away.

About the only problem that is problematic with QFeed is that it is only as timely as their source from S&P Comstock. The Boston servers with the new IP based feed seem to have licked that issue, the rest are still being fed by the slower link and during fast market conditions, the feed can be rather dramatically behind.