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 : All About Sun Microsystems -- Ignore unavailable to you. Want to Upgrade?

To: Scott McPealy who wrote (10427)	7/13/1998 10:33:00 PM
From: The Ox	Respond to of 64865

Correct me if I'm wrong, but TCP/IP is not native WinXX code, but added on.

To: Scott McPealy who wrote (10427)	7/14/1998 1:50:00 AM
From: QwikSand	Respond to of 64865

Come off it Scotty. "TCP/IP computing" might not be the most descriptive instant buzzword the 'computer industry executive' could have chosen, but you know what he means. All you need for distributed object-oriented Java computing is the ability to move java bytecode and random data over a wire. Underneath that, you have things that anyone is allowed to implement. With COM and DCOM and MTS, objects know about and take advantage of services in the underlying (Microsoft) O/S. You need plumbing underneath that only Microsoft is allowed to implement. (This is based on Microsoft's 100% bogus propaganda about what's required for good object performance, but that's another story, as is the "COM on Unix" fairy tale). So "TCP/IP computing" is just a somewhat clumsy expression for distributed computing among nodes that aren't all constrained to be Microsoft nodes. (And not Sun nodes either. Remember, unlike DCOM, anyone can implement anything in the Java world as long as they can prove they meet the spec. Tried that with Windows lately?) Can you say 'monopoly'? I agree with the 'computer industry executive'. Regards, --QwikSand