+1 I'm so delighted that we'll consider/are doing this :) I do think that Camel as a framework should take on the responsibility to hide these details from the user, user wants to invoke HTTP endpoints, the user doesn't care which version of HTTP Components/Netty/Jetty... is under the hood.
zoran On Thu, Jul 25, 2019 at 11:48 AM Claus Ibsen <claus.ib...@gmail.com> wrote: > > Hi > > So what has been bothering Camel 2.x users is that when they use http > they would likely use the camel-http4 component and then they should > use http4 as the component name. The old camel-http component is > deprecated as the http client it uses is EOL for many many years. > > So with Camel 3 on the way we have deleted the old camel-http > component and the camel-http4 component now has both http and http4 as > component names. > > I think we should rename the camel-http4 back to camel-http and then > favour using http as the component name, and then deprecate http4 (or > even remove it). > > Any thoughts? > > > -- > Claus Ibsen > ----------------- > http://davsclaus.com @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 -- Zoran Regvart
