My 0,02 $: I would add a warning on page [1] that new user should prefer to use camel-http4 over camel-http (as we did it already for iBatis). Camel-http should mark as deprecated and will be deleted in Camel 3.x. I would *NOT* rename camel-http to camel-http3 and camel-http4 to camel-http. This will confuse our users.
[1] http://camel.apache.org/http.html Best, Christian On Mon, Apr 9, 2012 at 8:18 PM, Johan Edstrom <seij...@gmail.com> wrote: > +1 > On Apr 9, 2012, at 10:05 AM, Hadrian Zbarcea wrote: > > > +1. I wanted to say the same thing. Dan beat me to it. > > Hadrian > > > > On 04/09/2012 12:02 PM, Daniel Kulp wrote: > >> On Monday, April 09, 2012 05:43:15 PM Claus Ibsen wrote: > >>> Its just that Apache iBatis moved out of Apache, and is no longer an > >>> Apache project. And therefore people should use the product hosted by > >>> MyBatis instead. And as Apache iBatis is retired, then that is fine > >>> with me to remove camel-ibatis in Camel 3.0. > >>> http://ibatis.apache.org/ > >>> > >>> The old http client 3.1 is very much still in use. It simply just > >>> works. And still other products and frameworks use it. > >>> http client 4.x has a very different API / configuration model / that > >>> is a bit pain in the ****. > >> > >> According to the hc website, 3.x is end-of-life: > >> > >> http://hc.apache.org/ > >> > >> (see very bottom) > >> > >> Thus, from my perspective, there is no difference between this and the > >> iBatis case. In neither case is there a community behind the > component to > >> support it. With iBatis, folks need to move to MyBatis. With http > client, > >> they need to move to 4.x. I'm fine keeping the 3.x version around > for > >> a little while to help people move, but for 3.0, we really need to make > sure > >> the DEFAULT is the version that is actually supported by the > communities. > >> > >> > >> Dan > >> > >> > >> > >> > >>> So I want to keep both of them. > >>> - camel-http > >>> - camel-mina > >>> > >>>> Regards > >>>> JB > >>>> > >>>> On 04/09/2012 03:27 PM, Glen Mazza wrote: > >>>>> Team, I noticed Camel is maintaining both an "HTTP" (using Apache > HTTP > >>>>> client 3.x) and an "HTTP4" component (using Apache HTTP client 4.x). > >>>>> For > >>>>> Camel 3.0, can/should the former be removed so only one component is > >>>>> maintained, with the latter component optionally being renamed to > HTTP > >>>>> in the process? > >>>>> > >>>>> Glen > >>>> > >>>> -- > >>>> Jean-Baptiste Onofré > >>>> jbono...@apache.org > >>>> http://blog.nanthrax.net > >>>> Talend - http://www.talend.com > > > > -- > > Hadrian Zbarcea > > Principal Software Architect > > Talend, Inc > > http://coders.talend.com/ > > http://camelbot.blogspot.com/ > >
