Take a Stand and Understand the Standard - HTML with Style | 6
Take a Stand and Understand the Standard
The first problem we are faced with is the problem of integration with HTML. As I said above, there is a distinction between Web pages that are used solely as applications and those that contain little interactive tools. This problem is not really a problem of choosing the tool for your application, however; it's a question of being able to embed the application into the HTML document. This can currently be accomplished easily for Java applets and ActiveX controls, but anything else either requires the OBJECT element, which as we all now remains unimplemented, or must rely on proprietary extensions to HTML. So the first thing that browser makers must do, immediately, is implement OBJECT. OBJECT has many other uses, such as embedding multimedia files into documents, and is sorely needed as a uniform way of embedding other media into HTML documents.
So we're left with a few ideas of how we define a Web-based application: a program, that is transmitted over the Internet, and runs on a user's machine, that allows the user to interact with a server. We need the program to be able to run on many platforms. We need to be able to easily write the program without resorting to expensive tools. And we need the program to integrate seemlessly with HTTP and URIs, as well as it to be embeddable in HTML documents.
Not currently, I'm afraid. At least, I wouldn't recommend it quite yet. It's quite plausible that you can use Java for these things, but you will be missing a few (very few) of your customers. Namely, those with text-based browsers, or browsers that don't support Java. It's not a big crowd; it's definitely a smaller crowd than those having problems with DHTML, but I'm a perfectionist and cannot possibly be happy with that. You might be.
Produced by Stephanos Piperoglou
Created: August 25, 1999
Revised: August 26, 2089