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.

Strategies & Market Trends : DAYTRADING Fundamentals -- Ignore unavailable to you. Want to Upgrade?

To: Richard Goodman who wrote (6293)	1/5/2000 9:24:00 PM
From: Dan Duchardt	Respond to of 18137

I guess the DSL discussion is a bit OT here, but since the topic seems to be of interest I hope you will all indulge a question: I only have dial up available at the moment, but DSL is coming and I might even be close enough to the CO. But I know that my connection to my ISP is good most of the time, and I do not overload my (almost) 56K bandwidth. The problem I have is that after packets leave my ISP's backbone provider (Qwest.net) and run through another backbone to my quote service (myTrack) I often get high error rates and slow return times that seriously degrade performance. I sometimes exit my quote s/w and start again so I will get a different server connected through a different backbone. (Not to throw stones, but sprintlink.net is consistently bad, ALTER.NET is much better, and cerf.net is usually the best and has the fewest hops.) I don't see that a bigger pipe to the first node in the path is going to help one bit. Am I missing something? Dan