W3C home > Mailing lists > Public > www-talk@w3.org > May to June 1996

Re: Java and HTML and well known socket numbers

From: Matthew James Marnell <marnellm@portia.portia.com>
Date: Tue, 04 Jun 1996 03:11:39 -0400
Message-Id: <199606040711.DAA09082@portia.portia.com>
To: MegaZone <megazone@livingston.com>
Cc: holtrf@destinyusa.com (Russell Holt), www-html@w3.org, www-talk@w3.org
:>Securely transacting Java applets from and *to* servers and executing the
:>applets on the server in a fully secured and sanitized environment.

Sorry, I missed this in the first reading.  Again, since nobody
has asked this question, I will.  Why are we talking about running
Java applets on servers?  Why did someone go through all that trouble
to make a largely portable (and since Sun just cinched up the bag
with it's 1.0.2 license, I don't think many other systems besides
the ones that Sun supports will have a JDK or other Java platform
that keeps up with the Spec) language?  Why are we going to use
Java instead of CGI if we're going to have to execute it back on
our servers anyway?

I'm afraid that something has gone awry, terribly awry here.  You see,
I can't think of any reason that anyone would be sending me anything
to run on the servers.  I can see someone downloading applets/apps
that reference another service on my servers, such as an applet that
uses the MsqlJava classes to talk to the mSQL daemon, etc.  Since
security is supposed to be built into Java in one of the upcoming
releases, that's taken care of.

So, what's the beef.  I've seen MZ talk about sending Java applets/apps
back and forth, but one it's there, has the class it needs to talk
back, why send one back?  Why send a whole big bloody applet back
when you can use any number of protocols to talk back and forth.

Edumicate me.

Received on Tuesday, 4 June 1996 03:12:08 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:32:58 UTC