[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [p2-dev] ECF provider based upon httpclient4/httpcomponents
Thanks Scott! (And the entire ECF Team). I've been using httpcomponents myself (for some other work), and IMHO it's the one we want to be using (since, as you said, it's the technology that's currently under active development).
Scott, what's involved from a p2 standpoint. Obviously the release engineering work to consume this provider and thorough regression testing. Is there development that will also need to be done, or does ECF take care of all the abstraction there? IIRC, none of the providers leak into p2, so from a p2 code standpoint, there really should be no difference. Is that correct?
On Thu, Sep 13, 2012 at 2:19 PM, Scott Lewis <slewis@xxxxxxxxxxxxx>
Hi p2 team,
ECF has an enhancement request to create a filetransfer provider based upon Apache httpclient4 (aka httpcomponents). See  and .
Thanks to the ECF contributors and committers, we have this provider working, and we are now building it and testing it with the ECF filetransfer test suite (we run this against all providers).
We would like to have p2/Eclipse eventually use this provider...or course after thorough regression testing...as well as testing against proxy configurations (e.g. NTLM2). We think that the httpclient4-based provider will be a much better base to go forward from...at least partially because the Apache httpclient4 codebase is under active development and maintenance, while httpclient 3.1 is not any longer.
To do this transition, however, we will need some help and cooperation from the p2 committers and/or community over this coming fall and winter. Assuming this fits in with p2's plans...Ian, Pascal, or others...please let me know how best to coordinate/accomplish this transition.
p2-dev mailing list
R. Ian Bull | EclipseSource Victoria | +1 250 477 7484http://eclipsesource.com