On Sun, Jan 30, 2011 at 11:01 PM, Christian Müller <christian.muel...@gmail.com> wrote: > Hello Claus! > > I added the missed wiki page and updated camel-http4 to use the Apache > HttpClient 4.1. > I realized that camel-http made some progression but camel-http4 not > (camel-http4 was forked in Camel 2.2). :-(
> Do you remember what the reason was to provide a new component instead of > "only" updating the existing one - maybe with API breaks? Do you remember Yeah Apache Http Client 3.1 / 4.x is very different from end user perspective. The API is not backwards compatible and 4.x has a now and very confusing configuration model. We tried upgrading 1 year ago and it was now possible. Also at that time some features wasn't implemented in 4.x that existed in 3.1. > whether HttpClient 4.0 doesn't support a feature HttpClient 3.x supports? > If it's only the configuration of the httpClient options, I will check which > options are affected. Also, users which uses the HttpClientConfigurer are > also affected, because HttpClient is an interface in HttpClient 4.x. But > maybe there are only a few changes we could add on the release notes (with a > "migration plan") and only maintain the camel-http component (which use > HttpClient 4.1) from Camel 2.7 onwards. It's really difficult to have two > components in sync over a long time... We should not migrate. We will keep camel-http and camel-http4 as 2 separate components. Then end user can decide which they wanna use. And they should co-exist, hence why camel-http4 uses http4/http4s in the scheme name. > If this is not an option for you, I will spend some time on camel-http4 in > Camel 2.7 so that both components are as similar as possible. > > [1] https://issues.apache.org/jira/browse/CAMEL-2608 > > Christian > Yeah it would be best if http and http4 have almost the same options in the endpoint uri offered by Camel. For example bridgeEndpoint and so forth. But of course there could be never features in http4 which doesnt existing in the old http component. -- Claus Ibsen ----------------- FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
