Re: RTT-Introspection and how to do it ?

Hey,
we had a discussion about the introspection today,
and came up with a second approach to this.

The idea was to add a flag to ChannelElementBase
bool isRemoteElement()
and a method
std::string getRemoteEndpointURI()

If we afterwards modify the ros and Corba::RemoteChannelElement,
to fill in the Information, we should have a solution that works
in all cases. And not tooling patching would be involved.

To gather the introspection information, the TaskContextServer (or
whatever else you use) would need to iterate over the channel elements
of the ConnectionManager and output it. Big plus, of there is a
BufferChannelElement in between, one could also ask it for its
fill status.
Thoughts on this ?
     Janosch


Am 24.03.2015 um 17:51 schrieb Sylvain Joyeux:
>> Egg vs. Hen. I need to know, what each of them would fill, to know how to
>> implement something that *can be used* in all these cases...
> The string is a very universal way to store any kind of information.
> Which is why I advocate for leaving the RTT part simple (list of
> key/value pairs).
>
>> AFAIK the standard (implicit) RTT::Corba nameservice does exactly
>> the same as orocos.rb.
> Except that orocos.rb is architectured so that multiple name services
> can be used. It namespaces task names based on how the task can be
> resolved (so that it can be re-resolved later). This is how orocos.rb
> integrates ROS transparently. It basically provides a
> TaskContext-compatible API and a ROS-based name service. And, by the
> way, it is a mandatory thing to have if you want to build multi-robot
> systems (even with CORBA).
>
> Sylvain


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