[dsdp-tm-dev] Service Discovery Beta for RSE 1.0 M3

[javier.montalvoorus@xxxxxxxxxxx]

Hi all,

I have posted a new version of service
discovery for RSE. The new features are:

• RSE 1.0 M3 compatible (tested with the CVS of 27/7/2006).
• New protocols and transports can be added through extension points.
• Service discovery is independent of RSE (packages org.eclipse.tm.discovery), and has a plugin for linking to RSE (org.eclipse.rse.discovery)
• The service discovery wizard only shows supported services (matching any subsystem id). All discovered services can also be shown as an option.

The provided packages for service discovery
are:

org.eclipse.tm.discovery.engine
Engine for the service discovery process

org.eclipse.tm.discovery.protocol
Contains the factory, interface and
extension point to define protocols

org.eclipse.tm.discovery.transport
Contains the factory, interface and
extension point to define transports

org.eclipse.tm.discovery.protocol..dnssd
Implementation of the DNS - Service
Discovery protocol

org.eclipse.tm.discovery.transport.udp
Implementation of the UDP transport

org.eclipse.tm.discovery.view
View to browse discovered services,
independent of RSE and enabled to launch the wizard page to start a new
service discovery processes.

org.eclipse.tm.discovery.wizard
Wizard pages for service discovery

org.eclipse.tm.discovery.model
org.eclipse.tm.discovery.mode.edit
EMF model for Service Discovery (requires
EMF 2.2.0) 

org.eclipse.rse.discovery
Link between RSE and the target management
packages.
It extends the extension point org.eclipse.rse.ui.newConnectionWizardDelegate
to provide a customised wizard for the Discovery system type. It
implies that a new systemType "Discovery" has to be created.
Once selected in the first RSE wizard page, it will start the new service
discovery wizard.


At the moment, RSE does not yet accept
creating a new host with a list of services (https://bugs.eclipse.org/bugs/show_bug.cgi?id=150265).
Until this issue is fixed, the service discovery facility of RSE has to
be used through the following workaround:

1- Each service (ftp,telnet...) that
wants to be discovered has to be registered as a systemType
2- The subsystem plugin implementing
the service has to have the service as a supported systemType
3-The id of the subsystem implementing
this service has to match the discovered service (ftp, telnet...)

The service discovery plugins can be
found  in https://bugs.eclipse.org/bugs/attachment.cgi?id=46888
The list of patches for registering
the Discovery systemType as well as the workaround for ftp and ssh
can be found in https://bugs.eclipse.org/bugs/attachment.cgi?id=46889

Please, contact me for any question
or feedback about the service discovery feature, or post your ideas in
the bugzilla entry for autodetect (https://bugs.eclipse.org/bugs/show_bug..cgi?id=140320)


Regards,

Javier Montalvo Orús
Engineering
Tools 
Symbian Software Limited.

Tel: +44 (0)207 154 1091

---

*******************************************************************
*** Symbian Software Ltd is a company registered in England and
Wales with registered number 4190020 and registered office at 2-6
Boundary Row, Southwark, London, SE1 8HP, UK. This message is
intended only for use by the named addressee and may contain
privileged and/or confidential information. If you are not the
named addressee you should not disseminate, copy or take any action
in reliance on it. If you have received this message in error
please notify postmaster@xxxxxxxxxxx and delete the message and any
attachments accompanying it immediately. Neither Symbian nor any of
its Affiliates accepts liability for any corruption, interception,
amendment, tampering or viruses occurring to this message in
transit or for any message sent by its employees which is not in
compliance with Symbian corporate policy. *************************
*********************************************