Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ecf-dev] Pending changes to rfc 119 impl

Scott Lewis wrote:
> 2) Add support for latest OSGI compendium/RFC 119 spec version (i.e. see

I can probably implement
over the next couple of days.

@Thomas the recent interface updates break SEN's contribution. Do you
intent on updating it?

> 3) Add extension points to the

IMO we should opt for OSGi services instead of EP. Not just because EP
don't support versioning, but also because most users of ECF RFC 119
will probably be more familiar with services rather then EPs.

> make it easily
> customizable.  Here are some initial thoughts:

>    a) A 'containerFinder' extension point.  Inside the
> DiscoveredServiceTrackerImpl is logic to find an appropriate client/peer
> container instance(s).  It currently looks through all known container
> instances (via the containerManager) and chooses one/several to use to
> lookup remote services.  This can/should be generalized, so that other
> plugins can help with the search (e.g. by creating new container
> instances, or etc).


>    c) I believe Markus had some ideas for extension points that would be
> notified on the service host/server side as well...and perhaps ideas for
> discovery impl extension points also.

It would be great if somebody would help implementing the dynamic dns
update portion of the new DNS-SD based discovery provider. With that
done we can easily add wide area discovery with SLP [1]. A contribution
for [2] would be highly appreciated too.


Back to the top