[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [ecf-dev] ECF 3.11.0 ... or 3.10.2
- From: Scott Lewis <slewis@xxxxxxxxxxxxx>
- Date: Thu, 3 Sep 2015 10:30:32 -0700
- Delivered-to: firstname.lastname@example.org
- User-agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
Without immediate objection, I'm going to schedule an ECF minor release
(3.11.0) for Monday, September 28. Unless others have contributions and
let me know in the next few days, it will consist of the new remote
service distribution provider as described below.
On 9/1/2015 4:44 PM, Scott Lewis wrote:
I've been working on a few additions to ECF remote services, with the
primary goal of making it easier for others to create and use new
Remote Service distribution providers (I would also like to make it
easier for people to create their own discovery providers, but for the
moment I am focusing on distribution providers).
To this end, what I've done so far is to create a new package in
org.eclipse.ecf.remoteservices API bundle:
package: org.eclipse.ecf.remoteservice.provider 
And added a new service interface: IRemoteServiceDistributionProvider,
an abstract impl class (RemoteServiceDistributionProvider and
Builder), and a helper class for providers that use adapters
I've been trying this new API out with two new distribution providers
that I've been working on:
What one can now do is use the whiteboard pattern to register an impl
of IRemoteServiceDistributionProvider, and this do the ECF setup to
allow for the use of that provider by ECF's RSA implementation.
[2a] and [3a] show two example uses of this provider API for the
Jersey and Hazelcast providers. As you can see, these create an
instance of IRemoteServiceDistributionProvider, and register that
instance as a IRemoteServiceDistributionProvider. That's all that's
Just to be clear, I can/could easily do this with DS doing the service
registration, and may yet do that. I want to have both programmatic
and DS examples.
Any thoughts/comments/criticisms appreciated.
I would like to release this provider API as part of some ECF
release. Technically, we need to have a minor release (including
review) with new API, although I might ask if this could be an
exception to the minor release process...or maybe expedited/simplified
in some way, since this is totally new ECF-specific API, and it's very
In any event, I wanted to find out what other committers and/or
contributors were thinking in terms of planning for a minor release.
It might be good to shoot for the third or fourth weeks in Sept...e.g.
21 or 28. Do others have additions that they would like to include
in 3.11.0 (or 3.10.2, depending upon what happens WRT the review,
etc)? For example, the new Zookeeper version in Orbit? Other things?
ecf-dev mailing list
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit