Re: RTT-Introspection and how to do it ?

> 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.
Right now, the goal would be to have something implemented in RTT that
*can be used* in all these cases. Having all of them fill them the
same way is a different topic.

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

If you want to be compatible with orocos.rb, you'll have to either
reimplement the naming service infrastructure (and pray that orocos.rb
and the C++ program share the same general configuration), or allow
the process to be given the NS namespace so that you can fill it.

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