Re: RTT-Introspection and how to do it ?

> 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
-- 
Orocos-Dev mailing list
[email protected]
http://lists.mech.kuleuven.be/mailman/listinfo/orocos-dev