hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Oleg Kalnichevski <ol...@apache.org>
Subject Re: HLCA: http-tunnel
Date Sat, 15 Jan 2005 17:06:11 GMT

The trouble is that any sort meaningful tunneling component most likely
would require at least rudimentary HTTP authentication support (http-
auth) and ability to retry HTTP requests (HttpMethodExecutor). Without
these features ProxyConnectMethod and HttpProxyHost would be of very
marginal use only.

What would you say if we moved HttpHost to http-common, kept
HttpMethodExecutor in http-common and moved ProxyConnectMethod and
HttpProxyHost to http-auth?


On Sat, 2005-01-15 at 13:51 +0100, Roland Weber wrote: 
> Hello folks,
> since the http-common component is meant to be useful
> by it's own for simple HTTP communication, we should
> give a little thought to those that might want to work on
> that simple level. As soon as they have to communicate
> through a proxy, they get a dependency on the http-client
> component, which depends on several other components.
> The dependencies seem even more excessive for people
> who only want to tunnel an application specific protocol
> through an HTTP proxy.
> What do you think about a new component for the
> proxy/tunneling support currently listed in http-client?
> * http-tunnel depends on http-common
>   - ProxyConnectMethod implementing HttpRequest
>   ? HttpProxyHost (only if HttpHost is moved to
>      http-common, to avoid dependency on http-client)
> cheers,
>   Roland

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

View raw message