Using the Java Plug-in
The
disadvantage of the
<APPLET>
tag is that you have to rely on the
browser’s Java interpreter. This is bad for two reasons:
The version of Java that is included in popular browsers lags the current version of the SDK. It was a painfully long time, for instance, between the release of SDK 1.1 and the time that SDK 1.1 was supported in Netscape and Internet Explorer. As a matter of fact, it hasn’t ever been fully supported in Internet Explorer—Microsoft has its own agenda, which may not match up with your “write once, run anywhere” aspirations.
The browser’s Java implementation has its own bugs and idiosyncrasies, which are different from the bugs and idiosyncrasies of Sun’s SDK. If you are hoping to run your applet on both Netscape and Internet Explorer, you will have to test it on both platforms to make sure you don’t run into any trouble. This is tedious and frustrating.
At the time of this writing, both browsers are moderately stable for SDK 1.1 development. As a developer, though, you’re probably itching to use all of those cool Java 2 features. What can you do? In light of the lawsuits brought by Sun and the Department of Justice, it is unlikely that Microsoft will ever support Java 2 in Internet Explorer. Netscape’s Java support in Navigator is likewise questionable, though for different reasons. In the foreseeable future, you can’t rely on Java 2 support in Navigator or Internet Explorer.
What Is the Java Plug-in?
Does that mean applets are dead? ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access