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.
Non-Tech : Quote.com QCharts

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: Richard Estes who wrote (5193)1/1/2000 4:33:00 PM
From: E. Davies  Read Replies (1) of 17977
 
I am a believer that net connections, cause a large number of problems.

The only logical way that the net connection is the source of our problems would be if qcharts has flaws in the programming. I'd give decent odds that this is the case. As a matter of fact in some cases it is obvious that the problem is exactly that- the qcharts program itself.

Why? Because the capacity required for any single person is *very* small compared to what the internet can handle. I normally can do fine with a steady 15k bit stream. The internet can *easily* handle that and does it all the time in video streaming.

In addition studying the nature of the error condition clearly shows that qcharts itself is flawed. The simple fact that clearing the temp files works is one proof and the fact that a chart will stay blank until you switch it to a new symbol is another.

Why does everyone seem to think that if someone sees a 400ms ping time that "explains" it? So it takes .4 seconds to get the packets instead of .2! Should the data stream be any less reliable? If so- it is the fault of the programming, not the fault of the net connection. Even if the net drops an occasional packet we should not see the level of collapse that shows up in qcharts every day.

The fact that you basically never see problems is indeed significant. If I were on the qcharts technical team I'd be sitting down with you to find out exactly why.

Possibilites:
1) There is a flaw in the server/qcharts protocol such that only net connections of a certain nature work. (Likely) Note that it is not a given *what* the nature needs to be- only that you seem to have it.

2) There is something about the style of how you use qcharts that avoids problems.

3) You are accessing a server that is not overloaded. Which server is 216.33.71.102? I gotta try that one. All of mine have *names*. Hmmmm...

4) There is something about your computer setup that bypasses the problems. Maybe it is because your equipment is not state of the art. Maybe it is because of some particular communications driver you have, the OS you are running, or even some communications program you have installed.

Any other possibilites?

Eric
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext