Mailing-List: contact httpclient-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "HttpClient Project" <httpclient-dev@jakarta.apache.org>
Received-SPF: neutral (asf.osuosl.org: local policy)
Message-ID: <445BB42E.5040806@dubioso.net>
Date: Fri, 05 May 2006 22:23:10 +0200
From: Roland Weber <http-async@dubioso.net>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.13) Gecko/20060428
MIME-Version: 1.0
To: HttpClient Project <httpclient-dev@jakarta.apache.org>
Subject: Re: [HttpComponents] Moving forward
References: <1146331437.8398.39.camel@localhost.localdomain>
	 <4453A51B.1020607@dubioso.net>
	 <1146333899.8398.47.camel@localhost.localdomain>
 <78f7873e0605021909x4eed5369if7b8fa375872e56d@mail.gmail.com>
In-Reply-To: <78f7873e0605021909x4eed5369if7b8fa375872e56d@mail.gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi Mike,

> The
> only caveat I would add is that I think it's important to keep the
> long term goals in mind, so that the code for cookies, auth, etc
> remains independent even if packaged together.

So what is the long term goal? Is it still to eventually have that
code in separate components if somebody volunteers to do the work?
Or is it being changed into having a well-designed package structure
for the code of the one single HttpClient component that takes care
of authentication, cookie handling, and connection management?

cheers,
  Roland

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