W3C home > Mailing lists > Public > www-jigsaw@w3.org > July to August 2000

RE: Use of deprecated APIs

From: Manty, George <George.Manty@compaq.com>
Date: Fri, 25 Aug 2000 09:44:20 -0500
Message-ID: <435D38D69707D4119BEF00508B6CAF2E035DD92F@cceexc01.cce.cpqcorp.net>
To: "'Michael Brennan'" <Michael_Brennan@Allegis.com>, www-jigsaw@w3.org
On the SSL front, take a look at Jigsaw-SSL:

 http://jcewww.iaik.tu-graz.ac.at/Applications/jigsaw.htm

George

-----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?

Thanks.

Michael Brennan
Software Engineer
tel: 415-355-5814
fax: 415-551-0601
michael_brennan@allegis.com
Received on Friday, 25 August 2000 10:44:58 GMT

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