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 : 3Com Corporation (COMS) -- Ignore unavailable to you. Want to Upgrade?

To: AreWeThereYet who wrote (9843)	11/8/1997 1:17:00 PM
From: Dee Jay	Read Replies (1) \| Respond to of 45548

"Diamond's solution is quite different, it actually use the 2 lines for 2 different purpose. It is specifily desgined for web browsing, using one ling for graphic and one for text transmission." - very clever solution, if it works. Dee Jay

To: AreWeThereYet who wrote (9843)	11/8/1997 1:44:00 PM
From: pass pass	Respond to of 45548

Graphic and text are coded into bits (0 and 1) and mapped to signal waveforms then sent through phone line. How do you know which bit belongs to text and which belongs to graphic? 2 lines merely means you have twice of bandwidth so you can send twice of amount of information. USR had this technology at least 8 months ago.

To: AreWeThereYet who wrote (9843)	11/11/1997 2:18:00 AM
From: Dick Smith	Respond to of 45548

Diamond's bonding product: Andy Chu comments, "I heard that Diamond's solution is quite different, it actually use the 2 lines for 2 different purpose. It is specifily desgined for web browsing, using one ling for graphic and one for text transmission." I hope not, and I think this unlikely. At what level within the TCP/IP stack can connections for the two different kinds of files be separated? No good place, as far as I can see. And why bother, anyway. What they're almost certainly doing is the same thing that just about every bonding vendor is doing, providing two channels for the data to pass over, which almost (some overhead, of course) doubles the throughput. This uses Multilink PPP. This feature requires support at the ISP... I'm not sure who (if anyone) supports Diamond's product, but it shouldn't be hard. The only problem, not always simple, is making sure that the two calls reach the same hub... this gets trickier when one of the two calls is made only under load. Here's a fairly unbiased reference on the whole thing: 56k.com My thoughts, of course, Dick