On Wed, Feb 17, 1999 at 10:37:53AM -0600, John Goerzen wrote:
> On Wed, Feb 17, 1999 at 09:51:51AM +0100, Chris Huebsch wrote:
>
> I know that Java is a VM, bytecode, etc. What I'm trying to say is that
> this is irrelevant -- HTML and the Web are simply the wrong paradigm for
> trying to deploy full-fledged applications.
Actually, this depends on the application. Using Java applets, you
*can* build full-fledged applications on the web in a meaningful way; it
is most appropriate for situations were your server and client process
are owned by the same entity (ie, a corporation) and you want to make
distribution and updates easier. This is a reasonable thing to do.
Some other situations also make sense. Consider, for example, a
tech-support webpage with a Java applet that lets you enter a
description of your problem and interact with the internal scheduling
mechanism to determine when to have a service visit? Or even one that
allows you to talk to the tech support guy (assuming you have sound set
up properly, a microphone, etc) and gives him the chance to poke around
your system looking for the problem?
There are uses for applets, believe me.
Regarding servlets, I wouldn't say they are necessarily technically
better than any other form of CGI (when coupled with an expert who
already understands them), but they have significant non-technical
benefits.
--
Matthew Hunter ([EMAIL PROTECTED])
