Mailing-List: contact commons-httpclient-dev-help@jakarta.apache.org;
 run by ezmlm
Message-ID: <3E3DC368.5000908@isisnetworks.net>
Date: Sun, 02 Feb 2003 20:18:32 -0500
From: Ryan Hoegg <rhoegg@isisnetworks.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.0.0) Gecko/20020530
MIME-Version: 1.0
To: Commons HttpClient Project <commons-httpclient-dev@jakarta.apache.org>
Subject: Re: more common classes need a home
References: <3E3DB4FC.7070102@sympatico.ca>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Jeffrey Dever wrote:

> There are still a bunch of classes that are in both HttpClient and 
> Slide.  In particular:
> Base64.java
> HttpsURL.java
> HttpURL.java
> URIException.java
> URI.java
> URIUtil.java
> URLUtil.java
>
> First of all, I think these should come out of Slide as part of their 
> migration to commons-httpclient which is still underway.
>
> Second, I thnk that these classes are too general to be part of 
> HttpClient.  They have use well beyond a http client, and so should be 
> available to other packages without requiring the commons-httpclient.jar.
>
> Do people agree with me?  If so, any idea where these could go?  
> Perhaps the root of org.apache.commons?  or a new commons-net 
> package?  put Base64 in commons-lang, and create a new commons-uri 
> package?

Base64 at least is in the Commons Codec package, which is currently in 
the sandbox.

In Apache XML-RPC, we recently discovered interoperability problems with 
Base64, and fixed them.  We will be pushing these changes upstream to Codec.

We are leaning towards introducing a dependency instead of rolling them 
into our JARs, as some of the contributors have found wierd classloader 
problems if the same class is in the classpath more than once.

I would agree with you for the others, they are useful to more than just 
this project.

--
Ryan Hoegg
ISIS Networks
http://www.isisnetworks.net