Remote services Generic provider that uses SSL transport

Earlier ECF general providers were based on raw TCP sockets. Thus encrypted communication through the ECF generic provider for OSGI Remote Service was not available. A new provider was developed to support secure/encrypted communication based upon SSL. See bug 391677

Rest server-side support for Remote Services

In previous versions of ECF, Rest API mostly supported the creation of OSGI Remote Service clients/consumers. This work on supports the creation and use of remote services on OSGi-based servers. Major additions can be found in org.eclipse.ecf.remoteservice.server bundle. Also some changes were made to the Restlet provider (available via ECF Github Repo.

ECF RemoteServiceTracker

ECF ServiceTrackers are used to discover registered services and then consume them. This RemoteServiceTracker allows the tracking of ECF RemoteService instances, which does not need the OSGi service registry to function (as normal service trackers do).

Contributions can be found in org.eclipse.ecf.remoteservice project.

API to allow customization of proxy creation

Earlier remote services proxy creation is done by using
AbstractRemoteService.createProxy/2
In order to customize the proxy creation it was necessary to subclass AbstractRemoteService and override createProxy. But with new contributions proxy creation can be dynamically customized using IRemoteServiceProxyCreator with an appropriate service ranking.

New filetransfer provider based upon Apache Httpclient 4.1

Active work on Apache Httpclient version 3.X has stopped, and Apache HttpComponents/Httpclient4 is now where active dev and bug fixing work is taking place. ECF has created and deployed a new provider based upon Httpclient 4, that will allow p2/Equinox/Eclipse platform to benefit from the new Apache Httpclient 4 work, including such desired features as full support for NTLM proxies, HTTP caching, improved proxy and credentials support, and active debugging.