Re: RTT-Introspection and how to do it ?

Am 24.03.2015 um 13:01 schrieb Sylvain Joyeux:
>> Ok with me, still I would like to have a common place to store the
>> information, and a standardized format would also be nice.
>>      Janosch
> Cf. the rest of the mail:
>   place: the policy, as a list of key-value pairs
>   standardized format: actually, not sure it makes sense as it will be
> tooling-specific information (i.e. each toolchain can define its own
> standardized set of keys, if multiple toolings want to share one then
> they can start discussing)
My current problem here is, that I would need to patch
the RTT::proxy::RemotePorts class to fill in the con tracing
information. The con tracing information should match the
one, being filled in by the orocos.rb layer and should also
be compatible with the ROS stuff, as the goal is to have
a tool that should work in all these cases.

I'm still a bit puzzled about what would be a good can tracing
information for the 'standard' RTT/Corba case. Your point was
that the task name that could be given to a namserver would
not be sufficient given the recent corba renaming patches.
What would be unique in this case ? A Corba URI ?
Greetings
     Janosch


-- 
  Dipl. Inf. Janosch Machowinski
  SAR- & Sicherheitsrobotik

  Universität Bremen
  FB 3 - Mathematik und Informatik
  AG Robotik
  Robert-Hooke-Straße 1
  28359 Bremen, Germany
  
  Zentrale: +49 421 178 45-6611
  
  Besuchsadresse der Nebengeschäftstelle:
  Robert-Hooke-Straße 5
  28359 Bremen, Germany
  
  Tel.:    +49 421 178 45-6614
  Empfang: +49 421 178 45-6600
  Fax:     +49 421 178 45-4150
  E-Mail:  [email protected]

  Weitere Informationen: http://www.informatik.uni-bremen.de/robotik

-- 
Orocos-Dev mailing list
[email protected]
http://lists.mech.kuleuven.be/mailman/listinfo/orocos-dev