W3C home > Mailing lists > Public > www-jigsaw@w3.org > September to October 2000

RE: Use of deprecated APIs

From: Manty, George <George.Manty@compaq.com>
Date: Wed, 6 Sep 2000 10:20:14 -0500
Message-ID: <435D38D69707D4119BEF00508B6CAF2E035DD96D@cceexc01.cce.cpqcorp.net>
To: "'Yves Lafon'" <ylafon@w3.org>
Cc: www-jigsaw@w3.org
I know this message was originally sent a long time ago, but I was wondering
if you could elaborate on why Jigsaw-SSLs mapping into Jigsaw is no longer
supported.

Also, are there any talks of developing an Open Source SSL component into
Jigsaw? 

Thank you,
George

-----Original Message-----
From: Yves Lafon [mailto:ylafon@w3.org]
Sent: Friday, August 25, 2000 9:56 AM
To: Manty, George
Cc: 'Michael Brennan'; www-jigsaw@w3.org
Subject: RE: Use of deprecated APIs


On Fri, 25 Aug 2000, Manty, George wrote:

> On the SSL front, take a look at Jigsaw-SSL:
> 
>  http://jcewww.iaik.tu-graz.ac.at/Applications/jigsaw.htm

Unfortunately, their mapping into Jigsaw is no longer supported, so if
they change their SSL API, you won't be able to upgrade.
But if someone would contribute integrating JSSE/JCE it would be more that
nice and of course part of upcoming releases :)

> -----Original Message-----
> From: Michael Brennan [mailto:Michael_Brennan@Allegis.com]
> Sent: Thursday, August 24, 2000 4:24 PM
> To: www-jigsaw@w3.org
> Subject: Use of deprecated APIs
> 
> 
> I am investigating using the Jigsaw HTTP client library in an application.
> There are a few issues I've encountered, and I'm wondering if anyone has
> addressed them or if there are plans for addressing them. One is the heavy
> use of deprecated APIs throughout the code. Are there plans on changing
> this? If not, if I go through the code and fix these, would there be
> interest in incorporating the changes back into the code base?
> 
> Another issue is lack of SSL support. At present, it looks like the socket
> is created via a "new Socket(...)" call within HttpBasicConnection. If
> HttpBasicConnection used a SocketFactory that could be supplied at
runtime,
> it would offer a great deal more flexibility and would make it (I believe)
> fairly easy to implement SSL support. Are there any plans for this or
> anything similar?

There is already another HttpConnection, HttpMuxConnection, done to test
MUX in the HTTP-NG framework, you just have to make Http<foo>Server and
Http<foo>Connection and set org.w3c.www.protocol.http.server to the class
of your server (default is HttpBasicServer).
For the server side, it would be a subclass of httpd.java like what IAIK
people did.
Hope this helps,

      /\          - Yves Lafon - World Wide Web Consortium - 
  /\ /  \        Architecture Domain - Jigsaw Activity Leader
 /  \    \/\    
/    \   /  \   http://www.w3.org/People/Lafon - ylafon@w3.org    
Received on Wednesday, 6 September 2000 11:20:50 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 9 April 2012 12:13:34 GMT