Silicon Investor (SI) -- The First Internet Community

STOCKTALK

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.

Non-Tech : Quote.com QCharts -- Ignore unavailable to you. Want to Upgrade?

To: paulr1 who wrote (10277)	10/31/2000 3:42:03 PM
From: stullbj	Read Replies (3) \| Respond to of 17977

On the new feed this does not happen nearly as often as on the 128k feed. Unfortunately, the problem today has caused the IP feed to start fluctuating between up and down for a few seconds at a time. The data that should have come through during the down period is lost (this includes any updates for MM bids/asks), resulting in the stale L2 quote. Paul, Appreciate the response, but it is still not clear why the Comstock problem is only affecting Quote.com users and not other users of other charting packages using the Comstock feed. Could you elaborate on the above quote? Do you mean that since Quote.com only has a 128K backup feed and that everyone else uses a much bigger backup feed and that is why Quote.com is having problems that the others are not? If so when do you plan on updating your backup feed to a bigger pipe? Since you are always having problems with the Comstock feed, the backup feed would need improvement as well since you use it almost as much as the Comstock feed. Right? Thanks, -Brian-

To: paulr1 who wrote (10277)	11/1/2000 1:33:30 PM
From: jebj	Read Replies (1) \| Respond to of 17977

>I am not aware of any plans to drop Comstock. The IP feed, apart from the issue today, works quite well. - Paul Guess I misunderstood what you said - Thought you had said the stuck BID/ASK on L2 was a comstock problem - now I understand you are saying it is your feed problem and not Comstock. Either way, this is a problem - for whatever reason - that does not seem to BE a problem on other feeds. Obviously, the upgrade on the Boston servers did not solve the problem - when can we expect a "pipeline" of the correct size to be in place to do so? jb