Creating a new package org.apache.commons.uri implies creating a new Jakarta Commons subproject called URI. Are you suggesting that we start a new project for this?
Instead of saying HttpURL should be useful outside of HttpClient, you should have a related set of classes that are useful outside of httpclient. It does not make much sense to created an Object Oriented reusable class which isolated from others in its package. HttpURL should use NameValuePair directly to provide for the simplest interface and reduce object conversion inside of HttpClient. Then HttpURL and NameValuePair can be taken out of HttpClient (if desired at some point) and used together in somthing else.
You could move these two classes into the httpclient.util package to clearly denote them as classes that can be removed into own subproject in the future.
Lets focus on making HttpClient clean, powerful and efficient right now.
-jsd
Sung-Gu wrote:
----- Original Message -----
From: "Ortwin Glück" <[EMAIL PROTECTED]>
Okay. But this class is in the package httpclient. If it was a genericYes, I think so.
class then it should be in a package unrelated to httpclient. I am still
So I have asked about it before I committed them that I don't know
which place would be ok.
This time, I suggest my recent URI related things to move to the new
package,
probably, org.apache.commons.uri.
+1
Or other suggestions?
Sung-Gu
-- To unsubscribe, e-mail: <mailto:commons-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:commons-dev-help@;jakarta.apache.org>
