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.
Technology Stocks : LINUX -- Ignore unavailable to you. Want to Upgrade?


To: Rar who wrote (1294)3/12/1999 3:50:00 PM
From: Mitch Blevins  Read Replies (2) | Respond to of 2617
 
I agree... bandwidth usage is a big drawback of the X protocol.

You can use a compressing proxy between machines, but it doesn't help _that_ much. The only way to really lessen the bandwidth load is to have the machines on each end of a connection have a common language for generic widgets. Instead of pushing all the pixels that show a combo-box across the network, the protocol would push a message like "Combobox:<selection1><selection2><selection3>".
The client would then have the smarts to interpret this and draw the combo box using whichever toolkit it had installed. This is how ICA, RDP, etc work. It is interesting that a logical conclusion of going in this direction is an XML/HTML type rendering language.



To: Rar who wrote (1294)3/12/1999 6:44:00 PM
From: Thomas A Watson  Read Replies (2) | Respond to of 2617
 
Rawn, I have several computers networked at home using 10 Megabit Ethernet. My Machines all run linux and the kiddies machines borg with exceed. I don't see any problems on my el-cheapo network and I could update to 100 megabits for a couple of hundred. I use a hundred at work and X screams across.

TOm Watson tosiwme