Please find the attached new NewAndNoteworthy page. I added the content in review slides. Also add more details which I could find. Sorry could not add any images since I could not come up with any. Also please make note that discussion regarding httpclient 4 provider from ECF [1] is still continuing. So please review that part thoroughly.
The current one (3.5.2) is called NewAndNoteworthy.html.
I don't think you have commit rights to the git repo...so...if you
get a copy of the NewAndNoteworthy.html and make changes to it
(for 3.6.0 release information), then if you just send to me e.g.
as email attachment...along with any new screenshots/images
referenced...in ./images/filename), I'll add the file to the git
repository.
Scott
On 3/7/2013 10:26 AM, tishan pubudu kanishka dahanayakage wrote:
Hi Scott,
I can help with
creating NewAndNoteworthy
page. But I need some advice such as where to log in and add
pages. Also not sure whether I have permission.
Status update on ECF 3.6.0 release...scheduled for next
Monday, March 11, 2013.
We've completed the release review, and the review has
passed successfully [1].
I've completed a release candidate build, done some install
and smoke testing myself, and this build is available here
[2]. If you can, help us out by doing some test installs
and smoke tests. If you find or encounter any difficulties,
please report with a major bug right away.
One thing remains to be done to support the release: create
a new NewAndNoteworthy page.
Are there any volunteers? The easiest way to go about it is
that you can take the previous one as a template, and use
the 3.6.0 review slides (i.e. the 'what's new to 3.6.0
release') to help fill out the content...along with some
additional prose...and sometimes screenshots...to explain
each of the new things...along with links to
bugs/enhancements.
Earlier ECF general providers were based on raw TCP sockets. Thus
secure communication through providers could not be done. So new
provider was developed to support secure/encrypted communication
based upon SSL. with this addition consumers can enjoy the luxury
of secure communication. Most of the work can be found in here.
Several additional classes can be found in org.eclipse.ecf.server
bundle. Those additions were made to support server-side usage of
this new provider.Also the execution environment was changed from
CDC 1.1 to jre 1.4 following the change.
In ECF 3.5.2 and lower, Rest API mostly support the creation of
OSGI Remote Service clients/consumers. But it would come in handy
also to add server-side support for registration of remote
services. This will allow the export of REST/Restlet API-based
services as ECF (and OSGi) remote services. Major additions can be
found in org.eclipse.ecf.remoteservice.server bundle. Also some
changes were made to Restlet provider.
ECF ServiceTrackers are used to discover registered services
and then consume them. But this ServiceTracker cannot be used to
track remote service. Solution is to come up with a
RemoteServiceTracker. RemoteServiceTracker can be used in the same
way as ServiceTracker to discover services.
Ex:
RemoteServiceTracker rst = new RemoteServiceTracker(...);
rst.open();
IRemoteService rservice = rst.getService();
//use service
Contributions can be found in org.eclipse.ecf.remoteservice project.
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.
As Httpclient version 3 (org.apache.commons.httpclient) has been discontinued, it forced eclipse platform to move into hc-httpclient version 4 (org.apache.http.client).
Because of the ECF provider architecture this was achieved through a new implementation of existing ECF file transfer API. Note that no API changes were necessary for
the change.