You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Brian Behlendorf <br...@hyperreal.com> on 1997/05/16 08:35:54 UTC
Re: JDK 1.* and HTTP/1.1 [Chuck McManis ] (fwd)
---------- Forwarded message ----------
Date: Wed, 14 May 1997 14:03:55 -0700
From: Chuck McManis <cm...@freegate.net>
To: Rodent of Unusual Size <co...@decus.org>
CC: David.Brownell@eng.sun.com, David.A.Brown@eng.sun.com,
Andrew.Shikiar@eng.sun.com, david.burnette@javaworld.com,
dbowen@doppio.eng.sun.com, cmcmanis@netcom.com, New-HTTPd@apache.org
Subject: Re: JDK 1.* and HTTP/1.1
Rodent of Unusual Size wrote:
> 4. I don't see how David Brown's assertion that there will be no
> problem when Apache 1.2 hits the streets can be true. Existing
> applications will need to be rebuilt using the updated class
> libraries first. N'est-ce pas?
My take on Dave's response is that he may believe that the 1.1 JDK
is in much more widespread use than it actually is.
Two statements are demonstrably true:
1) All applications based on the 1.0.2 JDK will break.
2) Any applet that utilizes URLConnection that is accessed
by a Netscape 3.x or Internet Explorer 3.x browser will
most likely break.
Given the incompatibilities between 1.1 and 1.0.2 and the lack of
'production' browser support, a whopping majority of the Java classes
out there find themselves landing on 1.0.2 based Virtual Machines.
--Chuck
(cmcmanis@netcom.com)
Re: JDK 1.* and HTTP/1.1 [Chuck McManis ] (fwd)
Posted by Alexei Kosut <ak...@nueva.pvt.k12.ca.us>.
On Thu, 15 May 1997, Brian Behlendorf forwarded something Chuck McManis wrote:
> My take on Dave's response is that he may believe that the 1.1 JDK
> is in much more widespread use than it actually is.
>
> Two statements are demonstrably true:
Um... No. They are both demonstrably false.
> 1) All applications based on the 1.0.2 JDK will break.
No. As someone (I forget whom) pointed out, the Java classes themselves
do not have the HTTP/1.1 problem, it's the peer classes that are used
by the particular application. Not all of them have this problem.
> 2) Any applet that utilizes URLConnection that is accessed
> by a Netscape 3.x or Internet Explorer 3.x browser will
> most likely break.
Again, wrong, given that Netscape 3.x implements URLConnection using
the standard Netscape HTTP routines, which work just fine with
HTTP/1.1.
--
________________________________________________________________________
Alexei Kosut <ak...@nueva.pvt.k12.ca.us> The Apache HTTP Server
URL: http://www.nueva.pvt.k12.ca.us/~akosut/ http://www.apache.org/