Java Applet breaks down ActiveX

Java Applet breaks down ActiveX
Sensational! Java Applet is not human, how can we kneel down? Just kneel down. How can we defeat ActiveX?

Once upon a time, Java Applet step ActiveX under the foot. ActiveX is not safe. Java Applet can construct Sandbox because of the technology of virtual machines. Java Applet can run in SandBox, and Sandbox can exclude any dangerous action of Java Applet, for example, IO for local files. For this reason, of course, because of the hype and hype of the Java camp, most companies have configured their firewalls to prohibit any ActiveX attacks. ActiveX on the Web page becomes synonymous with security vulnerabilities.

Java Applet really puts ActiveX under its feet. At the same time, it is precisely because of the success of the Applet that Java has become synonymous with the Internet era. A language prepared for small devices and online applets has finally become a full-featured language. It enters the enterprise level and forms its own development platform, making Microsoft unable to beat it. Microsoft had to transform its development language in an all-round way, more or less aligned with Java. As we all know, this is the source of the. NET development language. Without Java, it is impossible for VB to become VB. NET so quickly, and there will be no C #, or. NET Common Runtime. I'm afraid no one will disagree.

Java starts from Java Applet, and Java Applet starts from Netscape. Later, Internet Explorer followed up, and then all browsers must support Java Applet. Microsoft did not think much about Netscape, so Internet Explorer has been honestly supporting Java applets. However, Netscape does not appreciate this, So Netscape's support for ActiveX has been limited to the level of Plug-in installation, that is, unless you install a Plug-in, otherwise, ActiveX cannot be run in the Netscape Browser. Generally, users do not know how to install another software, or they do not know how to install the software. They also know how to install the software, but it is not installed for reasons such as troubles. Sorry, you cannot browse webpages with ActiveX.

Any website developer knows this very well. If they use ActiveX instead of Java Applet on a webpage, it is estimated that half of Internet users will not be able to use their website because they use the Netscape Browser. Under the customer-oriented consideration, only Java Applet can be selected to discard ActiveX.

This is simply an unequal treaty, but Microsoft was unable to fight back at that time.

Now it is different. On the one hand, Netscape has changed from a tiger to a cat. On the other hand, Microsoft won the lawsuit and does not need to load JVM in the operating system. Microsoft counterattacks. Currently, IE6.0 has reduced Java support to the Plug-in installation level. That is to say, you can run Java Applet only after installing IE and then installing a JVM on your own. For ordinary users, this can only cause inconvenience and is a kind of backend.

But for Microsoft, unequal treaties have become equal, only at the cost ....

Let's take a look at how IE6 supports Java Applet. To run a Java Applet on IE, Web developers can specify a certain version of Sun JVM Plug-in (which is specially developed for IE ), you can trigger IE to automatically download this Plug-in. For example, the following tag declares a Java Applet named com. cmpc. CMPCApplet3, which requires 1.4.1 or an updated sun jvm (Plug-in developed for IE ):

<Object classid = "clsid: CAFEEFAC-0014-0001-0003-ABCDEFFEDCBA"
Width = "320" height = "240" name = "CMPC"
Codebase = "http://java.sun.com/products/plugin/autodl/jinstall-1_4-windows-i586.cab#Version=1,4,1,mn">
<Param name = "code" value = "com. cmpc. CMPCApplet3">
<Param name = "cache_archive_ex" value = "preload; 1.0.0.4">
</Object>

After the JVM is downloaded and installed, IE runs the Applet automatically. Of course, the download and installation of JVM in each version only happens once. Unless another Applet requires another version of JVM, it does not need to be downloaded and installed again. This is not especially inconvenient, especially for users with high-speed Internet access conditions. But if you are using a 56 K Modem, this is a problem. You may need to find the jvm cd of this version and install it on your machine, then browse the page that requires the JVM.

Readers may not see: Where is Java? I ran a lot of questions, right?

Slow down. Take a closer look at the above labels. It indicates that the JVM is an ActiveX.

It's strange. The Plug-in of IE must be ActiveX. After JVM drops to the Plug-in level, it also drops to a Common ActiveX level. All Java applets are small programs running in this ActiveX.

A safer and more powerful Java Applet must depend on ActiveX to run. Strictly speaking, it is still running in an ActiveX.

Another thought is even more interesting. If the user continues to believe in the original publicity of the Java camp, the user's firewall will not let sun jvm, Which is ActiveX, wear it, you cannot allow IE to automatically install JVM. In that case, there is only one way out for the user: Find a CD and manually install it on each machine. However, based on the experience of Netscape users, no one is bothered to do so.

Tell me, is Java Applet kneeling?