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.

Technology Stocks : AUTOHOME, Inc -- Ignore unavailable to you. Want to Upgrade?

To: KailuaBoy who wrote (22718)	5/28/2000 3:06:00 AM
From: ahhaha	Read Replies (2) \| Respond to of 29970

It's my statement and you're right. @Home can transcend the cloud without forward technologies, but transcendence requires big bucks provided by sites. It isn't practical to implement what you suggest. People would rather wait than pay. They haven't been able to identify a compelling reason to change. "Directly linked to a core router on the 'bone" forgets that the @Home national private 'bone is not ubiquitous. You may have a route that gains direct access to the @Home 'bone, but you can't go on because the @Home 'bone load is maxed, so you still have to use another 'bone owner's segment and that puts you into the cloud. The Net is a mesh topology. Between two points there are many paths each with varying loads, acceptances, and capacities. The specialized server computers find the best or only path. That may or may not invoke access via a NAP to the @Home 'bone. If you have the @Home service, necessarily you will use the @Home 'bone up to shunt or up and back from the cloud. Can CNN co-locate so they can tap into the @Home bone? Yes, but that ain't cheap to enable and CNN can't identify enough revenue to justify it. Better to push the inconvenience of the cloud onto users and damn be to competitive considerations.