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: Ahda who wrote (17450)	12/2/1999 3:48:00 PM
From: Jay Lowe	Read Replies (1) \| Respond to of 29970

>> distributed server The question addresses @Home's ability to control hosting QoS of the web pages which themselves make up a web-based application. A web-based desktop application consists of a lot of web pages whose interaction when displayed on your PC create the effect of running a local application. The question is, to what extent can @Home offer QoS provisioning by placing the pages at various levels closer to the user? Assorted alternatives and variation exist. What little I can find suggests that they have the option of QoS control at two levels: the super-node level and the local caching server level. It appears that the super-node level (geographical service hub) is rather like a mirroring layer ... where the service hubs mirror some or all of the @Home and partner-specific content ... the terms "replicating and caching" are used which could mean several things. The local caching layer seems to accomplish generalized URL caching at the DSLAM level, within the headend boxes. I'm poking around for information bearing on the suitability/constraints of @Home's design for deploying server-intensive QoS solutions. Does anyone have any detailed technical specs on the @Home architecture? I'm looking for substantive differences between @Home's capability and that of the net caching people or the ubiquitous server farm people. How specifically can @Home do better? In addition to bring the customer to the table, of course. Just trying to know the unknowable here ...