Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Message-ID: <4F82FCA2.1000601@nanthrax.net>
Date: Mon, 09 Apr 2012 17:13:38 +0200
From: =?ISO-8859-1?Q?Jean-Baptiste_Onofr=E9?= <jb@nanthrax.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:11.0) Gecko/20120329 Thunderbird/11.0.1
MIME-Version: 1.0
To: dev@camel.apache.org
Subject: Re: Remove Camel HTTP component in Camel 3.0?
References: <4F82E3A8.50903@talend.com>
In-Reply-To: <4F82E3A8.50903@talend.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable

Hi Glen,

currently, the component Camel code is exactly the same, only the HTTP=20
client used is different.

I noticed (and Claus too) an issue on this component (it always uses a=20
CachedOutputStream which mean that a file is created in tmp dir at every=20
call).

+1 to rename http4 to http and flag "http3" as deprecated.

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). Fo=
r
> 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
>

--=20
Jean-Baptiste Onofr=E9
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com