Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [dsdp-tm-dev] Service Discovery Beta for RSE 1.0 M3

Hello Aaron,
I believe you'd want to write
 - An IConnectorService implementation for your agent protocol,
 - A SocketFactory creating sockets that write through your multiplexed
   channel instead of standard TCP/IP
 - And then integrate the FTP / TFTP / Telnet etc services that are going
   to come through Jakarta Commons/Net with your SocketFactory.
   You'd do that by writing SubsystemConfigurations for Files, Commands
   subsystems, which instanciate the standard subsystems and configure
   them for using Commons-Net with your custom ConnectorService and
Commons-Net is going to finish EMO review any time now. I think I'll
publish an RSE I-build as soon as it is integrated.

Martin Oberhuber
Wind River Systems, Inc.
Target Management Project Lead, DSDP PMC Member


From: dsdp-tm-dev-bounces@xxxxxxxxxxx [mailto:dsdp-tm-dev-bounces@xxxxxxxxxxx] On Behalf Of Spear, Aaron
Sent: Friday, July 28, 2006 5:47 PM
To: Target Management developer discussions
Subject: RE: [dsdp-tm-dev] Service Discovery Beta for RSE 1.0 M3

Javier et all,
Could you direct me to a good reference for Zeroconf? I have poked around a bit, and trying to read RFC's and such to figure this stuff out seems like a poor use of time. 
I am starting to work on a design for how to connect the TM to an existing agent on an embedded OS that has its own proprietary protocol.  Over this protocol, which goes over a single communication link (serial, tcp, whatever), multiple services may have their own protocols multiplexed on top of it.  e.g. a debugger, profiler, and then other common services such as ftp, tftp, telnet, etc.  I would like to be able to provide an implementation of whichever RSE components that I need to connect to this system (transport? and "protocols" for my proprietary/legacy debugging protocol for instance?)  Obviously I would like to reuse all the other stuff that is planned in TM.
Also, is anyone currently using LDAP for exploring and configuring a remote system?  That seems like another opportunity for a shared TM component that would benefit many.  Does it already exist?
Any direction is greatly appreciated!
Aaron Spear
Debug Tools Architect/Staff Engineer
Mentor Graphics


From: dsdp-tm-dev-bounces@xxxxxxxxxxx [mailto:dsdp-tm-dev-bounces@xxxxxxxxxxx] On Behalf Of javier.montalvoorus@xxxxxxxxxxx
Sent: Thursday, July 27, 2006 10:10 AM
To: dsdp-tm-dev@xxxxxxxxxxx
Subject: [dsdp-tm-dev] Service Discovery Beta for RSE 1.0 M3

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, 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:
Engine for the service discovery process
Contains the factory, interface and extension point to define protocols
Contains the factory, interface and extension point to define transports
Implementation of the DNS - Service Discovery protocol
Implementation of the UDP transport
View to browse discovered services, independent of RSE and enabled to launch the wizard page to start a new service discovery processes.
Wizard pages for service discovery
EMF model for Service Discovery (requires EMF 2.2.0)

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 ( 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
The list of patches for registering the Discovery systemType as well as the workaround for ftp and ssh can be found in

Please, contact me for any question or feedback about the service discovery feature, or post your ideas in the bugzilla entry for autodetect (


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. *************************

Back to the top