[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [ecf-dev] ECF status -- discovery
|
Hi Markus,
Markus Alexande Kuppe wrote:
<stuff deleted>
a given discovered service (via IServiceInfo). This is just a
thought. Although fairly simple now, there might be ways to make it
easier.
Are you talking about something like a more specific listener
registration?
That would be an idea...i.e. types/sub-types of listeners...for specific
service types. My thinking here is that it's just sort of cumbersome
code to write to (e.g.) match against a set of properties and/or a
IService id.
3) Markus and I spoke during today's conference call about possibly
adding to the discovery service browser view an extension point that
allowed other plugins to register themselves as interested in certain
types of services...and then being able to insert actions that the
user can/could invoke...e.g. invoke service. This would make it very
easy to test services published via the discovery API.
4) I would like to persue some demo applications for EclipseCon that
use/show the discovery API. Some initial thoughts:
a) Use the discovery view to discover and then invoke iTunes remote
control (iTunes has a remote control interface that is exposed via
zeroconf). This might make kind of a cool demo...running iTunes via
Eclipse.
b) Putting together the discovery API, SLP provider, and the r-OSGi
provider for the ECF remote services API. Perhaps an Equinox server
and/or an eRCP device interacting via discovery/remote services.
c) Discovering and accessing some Eclipse-based services...e.g.
PlatformAdmin (to diagnose and fix bundle installation problems),
update manager (e.g. to discover lan-based update sites and present
them in (e.g.) the list of available remote sites in update.
d) setup discovery of p2 meta-data and artifact repositories
e) others?
For 3) and 4) I'd need to get our service view into shape for
contribution. I'm not entirely sure that I can pull that off in time
for EclipseCon, though for a demo the code probably doesn't need to be
through the IP process.
Do you think you/your employer would be able to contribute to
ecf1.osusol.org CVS first, and allow us to work on it/prepare demos,
etc? With the expectation of going through the IP process later? Too
bad it's unlikely to be in Ganymede.
I've been looking at the current discovery view and contemplating making
changes to it to do 3 and 4...and it would certainly be a waste to do
such things twice.
Thanks,
Cheers
Markus
PS: I've just moved the jSLP provider and tests to dev.eclipse.org.
Consider the IP process for jSLP provider done. :) Next on my list is
jSLP itself.
Cool. Thanks for keeping all updated.
Scott
