Mailing-List: contact commons-httpclient-dev-help@jakarta.apache.org;
 run by ezmlm
Precedence: bulk
Reply-To: "Commons HttpClient Project"
 <commons-httpclient-dev@jakarta.apache.org>
Message-ID: <40044DE4.8060600@latte.harvard.edu>
Date: Tue, 13 Jan 2004 14:58:28 -0500
From: "Mark R. Diggory" <mdiggory@latte.harvard.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; rv:1.6a) Gecko/20031030
MIME-Version: 1.0
To: 
  Commons HttpClient Project <commons-httpclient-dev@jakarta.apache.org>
Subject: Re: EncodingUtils
References: <89881226-45E5-11D8-AEDD-00306557E112@u.washington.edu>
	 <27D038C9-45E7-11D8-AEDD-00306557E112@u.washington.edu>
	 <400444D1.4020103@latte.harvard.edu>
 <1074022007.29123.29.camel@localhost.localdomain>
 <400449B0.4070602@latte.harvard.edu>
In-Reply-To: <400449B0.4070602@latte.harvard.edu>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Another feature of interest is the ContentType class in contributions, I 
suspect this should be more dependent on some general mimetype 
resolution functionality possibly via JAF or some comparable standard 
mimetype mapping library. This is something I'm researching as well for 
codec or lang (or possibly a new "mime" library).

-Mark

Mark R. Diggory wrote:

> Lol, I was trying to catch up with you...
> 
> Some of the stuff now in encodingUtil is dependent on HttpClient 
> NameValuePair etc. and seems specifically for managing the 
> encoding/building of query strings.
> 
> The ASCII stuff is just dependent in that it throws HttpclientError's
> 
> I suspect the later will be usefull to move out, while the former will 
> be difficult without added complexity.
> 
> I wonder what the best "design pattern" is for the ASCII conversion 
> stuff. Is ASCII conversion to be considered "encoding" or string 
> "translation"
> 
> See CharSetUtils in [lang]:
> http://jakarta.apache.org/commons/lang/api.1.0.1/org/apache/commons/lang/CharSetUtils.html#translate(java.lang.String,%20java.lang.String,%20java.lang.String) 
> 
> 
> -Mark
> 
> Oleg Kalnichevski wrote:
> 
>> Mark,
>> Ironically, I just responded to your message on the commons-dev mailing
>> list. I do think that EncodingUtil would fit quite well in codec
>>
>> Cheers,
>> Oleg
>>
>>
>> On Tue, 2004-01-13 at 20:19, Mark R. Diggory wrote:
>>
>>> Hey Guys, I didn't realize you were already doing this,
>>>
>>> http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25431
>>>
>>> I should pay more attention to the bugzilla. I posted a message 
>>> eariler today approaching the issues of HttpConstants encoding 
>>> methods and there usefullness outside of HttpClient on the Commons 
>>> developer list.
>>>
>>> Do you guys think that the Ascii stuff in EncodingUtil could 
>>> eventually move out into something like lang or codec?
>>>
>>> Cheers,
>>> Mark
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: 
>> commons-httpclient-dev-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: 
>> commons-httpclient-dev-help@jakarta.apache.org
>>
> 

-- 
Mark Diggory
Software Developer
Harvard MIT Data Center
http://osprey.hmdc.harvard.edu

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-httpclient-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-httpclient-dev-help@jakarta.apache.org