|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?