| Re: [equinox-dev] Finding a running instance |
|
Hi Jeff, Thomas, and Alexander, I don't want to sound too much like a broken record, but someone has to be the ECF advocate. :) The discovery API for ECF [1] (an API bundle...no implementation) is (by my definition) low overweight/low dependencies (i.e. the org.eclipse.ecf.discovery jar is 12K and it depends upon equinox common and CDC1.0/Foundation 1.0 only). It can accomodate other providers (it already has zeroconf-based provider, one ECF committer has worked on impl using JXTA, we would love to use JINI to implement discovery, UPnP, etc), and there is a Google SOC student to do local-only service discovery provider for auto configuration: http://wiki.eclipse.org/An_auto-configuration_plugin_for_Eclipse This sounds like it might be immediately useful/relevant for Thomas' requirements...but I'm not completely sure. I would guess that Alexander's discovery protocol implementation could/would also be implementable as an ECF discovery API provider, but as yet I don't know enough about it to say for sure. If not, we would enhance the API to accomodate. We would welcome such a contribution and collaboration, of course. FWIW, I don't, however, think it's a great idea to have multiple projects all trying to define a service discovery API based upon their particular discovery protocol. Thanks, Scott [1] http://wiki.eclipse.org/index.php/ECF_API_Docs#Discovery_API Jeff McAffer wrote:
|