[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [ecf-dev] httpclient 4 for rest API
|
Hi Folks,
I've created this enhancement for this issue:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=403675
On 3/18/2013 10:40 AM, Scott Lewis wrote:
Hi Folks,
As part of our 3.6.0 minor release done last Monday (11), ECF
contributed a new filetransfer provider to Equinox/p2 [1]. This
provider is based upon the Apache Httpclient 4 codebase, rather than
the Apache httpclient 3.1 codebase, which we/p2/Eclipse have been
using previously.
Currently, the ECF rest API uses/depends upon the httpclient 3.1
codebase. Specifically, see the dependencies in
org.eclipse.ecf.remoteservice.rest bundle.
ECF consumers will still be able to use httpclient 3.1 fine, as all of
the necessary plugins are in our repo...meaning that since they won't
get those plugins from new Eclipse versions, they will get them from
our repo when installed.
In the med to long term, however (e.g. Kepler simultaneous release),
it would be nice if we could move the
org.ecilpse.ecf.remoteservice.rest bundle to httpclient 4. I've
noticed that the httpclient4 'requestentity' classes have changed name
(e.g. what was 'RequestEntity' in httpclient 3.1 is now HttpEntity in
httpclient 4). This means that some of the API in
org.eclipse.ecf.remoteservice.rest will have to change.
Are there committers and/or contributors that are interested in making
these changes to move the ECF rest API from httpclient 3.1 to
httpclient 4...in the Kepler timeframe? Or are there folks that
would like to work with me to do it?
Thanks,
Scott
[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=337449
_______________________________________________
ecf-dev mailing list
ecf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ecf-dev
