Return-Path: Mailing-List: contact commons-httpclient-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list commons-httpclient-dev@jakarta.apache.org Received: (qmail 50851 invoked from network); 7 Feb 2003 18:37:43 -0000 Received: from mxout2.cac.washington.edu (140.142.33.4) by daedalus.apache.org with SMTP; 7 Feb 2003 18:37:43 -0000 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h17IbkGD002489 for ; Fri, 7 Feb 2003 10:37:46 -0800 Received: from u.washington.edu (ss02.co.us.ibm.com [32.97.110.67]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h17Ibfuo005557 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for ; Fri, 7 Feb 2003 10:37:46 -0800 Message-ID: <3E43FCE5.1090004@u.washington.edu> Date: Fri, 07 Feb 2003 13:37:25 -0500 From: Michael Becke User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3a) Gecko/20021212 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Commons HttpClient Project Subject: Re: Propose a new commons-uri package References: <3E43EFB4.3090504@sympatico.ca> In-Reply-To: <3E43EFB4.3090504@sympatico.ca> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Sounds like a good plan. I am happy to help if needed. One quick question regarding the HttpURL and HttpsURL classes. I mentioned this earlier when you were discussing the commons-uri package. Are these classes needed and would we want to bring them in to a new package? Mike Jeffrey Dever wrote: > > > This is just a draft regarding factoring out the URI based code in > HttpClient into its own dedicated package. Please comment. > > (0) rationale > > The concept of a URI is prevelent in networking. A specific form of > URI, a URL is used ubiquitously across the internet. Currently > HttpClient houses the URI and URL based classes, but these have much > broader use. This common functionality should be housed in its own > dedicated, small, reusable package. Any projects that require URI, URL > or URN functionality can do so by importing a small, focused package, > commons-uri.jar. > > (1) scope of the package > > The package shall provide a complete java implementation of RFC2396. > This includes the URI as well as URL and URN classes and utilities. The > implementation will be fully character set aware. > > (1.5) interaction with other packages > > Have no dependancies beyond the standard java packages. > > * > > (2) identify the initial source for the packages > > Various classes in common from from Commons HttpClient Jakarta Slide. > > (2.1) identify the base name for the package > > org.apache.commons.uri > > (2.2) identify the coding conventions for this package > > The code uses the conventions from the Jakarta Commons. > > (2.1) Identify the initial file structure > > jakarta-commons/org/apache/commons/uri > > uri/ > URI.java > URIUtil.java > URIException.java > url/ > HttpsURL.java > HttpURL.java > urn/ > (3) identify any Jakarta-Commons resources to be created > > (3.1) mailing list > > commons-dev@jakarta.apache.org > > (3.2) CVS repositories > > jakarta-commons/uri > > (3.3) Bugzilla > > The package should be listed as the uri component under the > Jakarta-Commons Bugzilla entry. > > (4) identify the initial set of committers to be listed in the Status File. > > Jeff Dever (jsdever) > Sung-Gu Park (jericho) > others? > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: > commons-httpclient-dev-unsubscribe@jakarta.apache.org > For additional commands, e-mail: > commons-httpclient-dev-help@jakarta.apache.org >