You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by Ortwin Glück <or...@nose.ch> on 2005/01/12 09:58:20 UTC
4.0 Requirements: Proxy chains
In our architecture draft at
http://wiki.apache.org/jakarta-httpclient/HttpClientApiRedesign
we should include proper architecture support for proxies and proxy
chains. This involves storing authentication information along the proxy
chain as well. We definitely need more than just a ProxyConnectRequest
to achieve that.
Motivated by Roland Weber, I find the HttpState class bad. Especially
the inheritance hierarchy seems weird. Why would HttpState (which sounds
very general) extend a CookieStore (which sounds very specific)?
Ortwin Glück
--
_________________________________________________________________
NOSE applied intelligence ag
ortwin glück [www] http://www.nose.ch
software engineer
hardturmstrasse 171 [pgp id] 0x81CF3416
8005 zürich [office] +41-1-277 57 35
switzerland [fax] +41-1-277 57 12
---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: httpclient-dev-help@jakarta.apache.org
Re: 4.0 Requirements: Proxy chains
Posted by Oleg Kalnichevski <ol...@apache.org>.
On Wed, Jan 12, 2005 at 03:44:48PM +0100, Roland Weber wrote:
> Hi Oleg,
>
> what's wrong with having an InMemoryCookieStore in
> http-cookie and a StdCredentialsProvider in http-auth?
>
Roland,
I see nothing wrong with that either.
Oleg
> When I first started using HttpClient (2.0 API), my
> biggest problem was getting rid of cookie handling.
> I know it can be switched off by now, but I still don't
> like the idea of having to pass in an object that might
> get modified, if I don't want it to be modified.
>
> cheers,
> Roland
>
>
>
>
> Oleg Kalnichevski <ol...@apache.org>
> 12.01.2005 15:38
> Please respond to
> "HttpClient Project"
>
>
> To
> HttpClient Project <ht...@jakarta.apache.org>
> cc
>
> Subject
> Re: 4.0 Requirements: Proxy chains
>
>
>
>
>
>
> Odi, Roland
>
> I wholeheartedly agree HttpState in its current form must go. I really
> like tie idea to replace it with CredentialsProvider and CookieStore
> interfaces and encourage the users to provide their own application
> specific implementations. This said we still have provide a simple in
> memory cookie store and a simple credentials store and I see no big deal
> combining those two stores for the sake of simplicity.
>
> class InMemoryHttpState implements CookieStore, CredentialsProvider
>
> Oleg
>
> On Wed, Jan 12, 2005 at 10:08:41AM +0100, Roland Weber wrote:
> > Hi Ortwin,
> >
> > > Motivated by Roland Weber, I find the HttpState class bad. Especially
> > > the inheritance hierarchy seems weird. Why would HttpState (which
> sounds
> >
> > > very general) extend a CookieStore (which sounds very specific)?
> > >
> > It was supposed to implement CookieStore and CredentialProvider,
> > thereby pulling both functionalities together into one class.
> >
> > cheers,
> > Roland
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: httpclient-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: httpclient-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: httpclient-dev-help@jakarta.apache.org
Re: 4.0 Requirements: Proxy chains
Posted by Roland Weber <RO...@de.ibm.com>.
Hi Oleg,
what's wrong with having an InMemoryCookieStore in
http-cookie and a StdCredentialsProvider in http-auth?
When I first started using HttpClient (2.0 API), my
biggest problem was getting rid of cookie handling.
I know it can be switched off by now, but I still don't
like the idea of having to pass in an object that might
get modified, if I don't want it to be modified.
cheers,
Roland
Oleg Kalnichevski <ol...@apache.org>
12.01.2005 15:38
Please respond to
"HttpClient Project"
To
HttpClient Project <ht...@jakarta.apache.org>
cc
Subject
Re: 4.0 Requirements: Proxy chains
Odi, Roland
I wholeheartedly agree HttpState in its current form must go. I really
like tie idea to replace it with CredentialsProvider and CookieStore
interfaces and encourage the users to provide their own application
specific implementations. This said we still have provide a simple in
memory cookie store and a simple credentials store and I see no big deal
combining those two stores for the sake of simplicity.
class InMemoryHttpState implements CookieStore, CredentialsProvider
Oleg
On Wed, Jan 12, 2005 at 10:08:41AM +0100, Roland Weber wrote:
> Hi Ortwin,
>
> > Motivated by Roland Weber, I find the HttpState class bad. Especially
> > the inheritance hierarchy seems weird. Why would HttpState (which
sounds
>
> > very general) extend a CookieStore (which sounds very specific)?
> >
> It was supposed to implement CookieStore and CredentialProvider,
> thereby pulling both functionalities together into one class.
>
> cheers,
> Roland
---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: httpclient-dev-help@jakarta.apache.org
Re: 4.0 Requirements: Proxy chains
Posted by Oleg Kalnichevski <ol...@apache.org>.
Odi, Roland
I wholeheartedly agree HttpState in its current form must go. I really
like tie idea to replace it with CredentialsProvider and CookieStore
interfaces and encourage the users to provide their own application
specific implementations. This said we still have provide a simple in
memory cookie store and a simple credentials store and I see no big deal
combining those two stores for the sake of simplicity.
class InMemoryHttpState implements CookieStore, CredentialsProvider
Oleg
On Wed, Jan 12, 2005 at 10:08:41AM +0100, Roland Weber wrote:
> Hi Ortwin,
>
> > Motivated by Roland Weber, I find the HttpState class bad. Especially
> > the inheritance hierarchy seems weird. Why would HttpState (which sounds
>
> > very general) extend a CookieStore (which sounds very specific)?
> >
> It was supposed to implement CookieStore and CredentialProvider,
> thereby pulling both functionalities together into one class.
>
> cheers,
> Roland
---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: httpclient-dev-help@jakarta.apache.org
Re: 4.0 Requirements: Proxy chains
Posted by Roland Weber <RO...@de.ibm.com>.
Hi Ortwin,
> Motivated by Roland Weber, I find the HttpState class bad. Especially
> the inheritance hierarchy seems weird. Why would HttpState (which sounds
> very general) extend a CookieStore (which sounds very specific)?
>
It was supposed to implement CookieStore and CredentialProvider,
thereby pulling both functionalities together into one class.
cheers,
Roland