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


To: Chris McConnel who wrote (8847)4/6/1998 12:42:00 PM
From: micromike  Respond to of 64865
 
So I ask you again, what advantages are there to running java apps on the client?

Two reasons is bandwidth saving on the network and cpu processing savings on the server. When you use Java applications the thin clients do the majority of the processing. The bandwidth demand is the heaviest only when the application is first loaded from the server. Basically you are distributing the work load to the clients and unloading the work from the server.

When Bandwidth increases in the future and Java gets better performance I can see a day when heavy duty applications can run on a thin clients.

JMHO
Mike



To: Chris McConnel who wrote (8847)4/6/1998 12:45:00 PM
From: Kashish King  Read Replies (2) | Respond to of 64865
 
What X Window lacks is the ability to execute application code on the client. I've already explained that to you. Java was designed to fill that deficiency. It was designed as a secure, robust, portable, object-oriented system for distributed computing. Technically it's a solid choice. Politically, Java is an open standard with the blessing of ISO and 90% its 20 plus member countries versus being a proprietary holding of an operating system monopoly. Practically it's has the support of Sony, Motorola, IBM, Oracle, thousands of smaller companies and over half a million individual developers.

Really, the only valid question you have is What is the value of executing code on the client device?, not whether Java is the best environment for doing which is a given for reasons I've already outlined. I am tempted to offer duh as an answer but let me continue. Java software is designed to control intelligent devices, not just dumb-ass monitors and dumb-ass keyboards. How the hell is the server supposed to control your device once it has interpreted a control function in your application? Moreover, the aggregate power of multiple client devices can quickly approach that of a large server, even a supercomputer. The idea is to leverage that power in a distributed manner such that clients handle localized issues locally. Note that they are adding printer support to Java which is an ass-backward but necessary step to leverage existing printer devices.

BTW, Microsoft claimed, not long ago, that the notion of running any client software on the server was brain-dead. Clearly the notion of running all of your software on the server is brain-dead and myopic, but that's not what Java is about.



To: Chris McConnel who wrote (8847)4/6/1998 3:24:00 PM
From: micromike  Read Replies (2) | Respond to of 64865
 
For all the non believers that think Java isn't important to Sun read this. Java is very important to Sun.

Sun Hardware President Outlines Strategy
techweb.com
"We have to make the notion of network computing a reality," Jabbar said. "Every device that can be networked will be in the next three to five years. I think the PC devices will be far outnumbered by other devices." He envisions a time when everything from a cell phone to television to an airline seat will be networked.

Jabbar said the only thing preventing this is better bandwidth. Sun will push Java as the solution to run these devices independently of applications. "We have to make Java a reality in the enterprise," said Jabbar. "We have to take Java to the next level in the enterprise.
---