[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [ecf-dev] ServiceTracker for remote services
|
Hi all,
I'm using ECF over XMPP with an Jabber-Server. What I need is the
functionallity similar to an OSGi ServiceTracker. Is there something
comparable in ECF?
When I start my application I need the ability:
1. to search for remote services already provided by my online clients
2. I also want to be informed about new service registrations if a new
client logs in and offers his remote services
Can the ECF ServiceDiscovery-API be used to deal with this problem? If
yes, how would I use the ServiceDiscoveryAPI to create a
ServiceTracker for ECF-remote-services? I basically need the
ServiceTracker to call bindService(...) and unbindService(...) methods
in order to handly the dynamic. Can someone please point me to some
code snippets?
Cheers,
Eugen
Am May 4, 2009 um 21:35 schrieb Scott Lewis:
Hi Folks,
The Galileo Release Train is heading toward the station: http://wiki.eclipse.org/Galileo_Simultaneous_Release
The platform Milestone 7 was last Friday (May 1) and ECF's M7 build
is due tomorrow (Tues May 4).
Just for clarification over the next several weeks, I thought I
would outline how I expect/hope things to go.
1) As of M7, we/ECF are under API freeze, as per our ramp-down
policy [1]. This means no API additions/changes after tomorrow,
without following the procedure outlined in the ramp-down policy.
2) As of RC1+2 (May 19), we will be under UI freeze as well. So we
have *two weeks* to get *any* changes into the ECF example apps/UI.
3) I (Scott) am planning on doing the M7 and RC builds...on the
*Monday* before...in the evening (pacific time). If others wish to
be involved in this, please let me know...as I have no great love of
doing this :).
4) The automated (and forced) build puts notifications to ecf-build
@ eclipse.org mailing list. I encourage all committers to subscribe
to this mailing list, so that they can get notifications of builds
as/when they occur...and if any build breakage occur can be ready to
respond.
5) Any build breakage will need to be addressed immediately (and
I'll come looking for you).
6) Please assign yourself any bugs that you are able to/are planning
on addressing.
7) Please communicate via a bug/enhancement request *and* this list
for any planned changes between now and Galileo. For example, if
you are planning to address some bug/bugs, just send a quick note to
this list to that effect, so that others are aware of your
intentions. If you are in doubt about whether anyone else cares,
please err on the side of more verboseness...that is, please send
the message/post to the bug.
8) We will create a branch for ECF 3.0/Galileo soon (I'm currently
targeting May 20/RC2)...as we are currently building ECF 3.0 from
HEAD. When the changeover to the branch occurs, remember that it
will be necessary to make sure that any bug fixes are applied to
*both* HEAD and the ecf3.0 branch. There will be more on the branch
procedures as we get close to May 20.
If you have any questions about anything, please bring them up here/
in public, so that everyone can contribute.
Thanks,
Scott
[1] *http://wiki.eclipse.org/ECF_3.0.0/Galileo_Ramp-Down_Policy
*
_______________________________________________
ecf-dev mailing list
ecf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ecf-dev
