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 : MSFT Internet Explorer vs. NSCP Navigator -- Ignore unavailable to you. Want to Upgrade?

To: damniseedemons who wrote (18157)	3/24/1998 11:13:00 PM
From: Kashish King	Respond to of 24154

Can anyone explain to me the benefits/use of "Java on the server side"? I'm don't fully understand it. Thanks. Microsoft's distributed component architecture is sort of an ad hoc mish-mash of afterthoughts but then Microsoft has always been well below par on the design front in general, and object-oriented design in particular. Although the pile of Windows-only experimental junk may find a market, it's so excruciatingly badly done that it's being rapidly overtaken by Java Beans and now Enterprise Java Beans. When we're talking about server-side Java, we're talking about Enterprise Java Beans. That is, distributed components which can bridge legacy database resources but which can also present a coherent, homogeneous set of services to Java applications running across the network, but which live on the server. The reason for Java on the server is to extend the homogeneous view which Java programers already enjoy on the client. Not a few DLLs and a few C++ components hacked into COM and topped off with some cruddy Visual Basic code and a slew of C language SDK calls; rather, a clean, consistent, homogenous environment of Java components and services.