It makes sense, we can rename/remove the http component as soon as
commons-httpclient 3 will be removed/fully deprecated.
Regards
JB
On 04/09/2012 05:43 PM, Claus Ibsen wrote:
On Mon, Apr 9, 2012 at 5:13 PM, Jean-Baptiste Onofré<j...@nanthrax.net> wrote:
Hi Glen,
currently, the component Camel code is exactly the same, only the HTTP
client used is different.
I noticed (and Claus too) an issue on this component (it always uses a
CachedOutputStream which mean that a file is created in tmp dir at every
call).
+1 to rename http4 to http and flag "http3" as deprecated.
-1 to rename. It will just confuse people when upgrading.
For example we have a similar situation with mina / mina 2.x. There is
a ton of users that use Mina 1.x as it simply works for them.
All together I dont see a reason to take that away from people. They
are both still a part of Apache.
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 ****.
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
--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
