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 02:57:12 -0400
Message-Id: <199606040657.CAA08961@portia.portia.com>
To: MegaZone <megazone@livingston.com>
Cc: holtrf@destinyusa.com (Russell Holt), www-html@w3.org, www-talk@w3.org
:>Once upon a time Russell Holt shaped the electrons to say...
:>>What does it mean to be "optimized to serve Java applets"?
:>>I can see an advantage in having a lean server which does nothing but
:>>serve GET requests for java applets. It skips all the extra baggage
:>I was thinking in terms of a lean server that handles Java and doesn't deal
:>with the other types of content.  Expecially in an environment where Java
:>Terms are in heavy use (IBM is considering replacing 3270s with Java Terms
:>for example, amongst many other such concepts).  Also the server could be
:>written with a much tighter, less-flexible security model to make for
:>the fewest number of possible leaks.  This is rather important when you
:>start accepting PUTs on applets to run on the server.

Okay, since nobody else has asked yet.  What's stopping you from putting
httpd's whatever port you see fit and adding that to your URL for that
specific content type.  Go find the documentation on which ports do
what, and pick one that isn't being used.  I have no problem personally
with one httpd doing it's job serving up all the content from one
single process.  I got it running, it's there already, it's doing what
it was built to do, I don't have to add anything new to /etc/services,
I don't have to find the best server, download it, configure it.  It's
already there, it works.  If it ain't broke, don't fix it.

Received on Tuesday, 4 June 1996 02:57:53 UTC

This archive was generated by hypermail 2.4.0 : Monday, 20 January 2020 16:08:20 UTC