Re: RTT-Introspection and how to do it ?

... coming back to my previous point:
 - the connection manager and channels APIs are private and should not
directly be accessed for this purpose

Moreover, if you aim is to make the connection info feature available
to everyone, then adding it to the public API would make sense.

How it then gets exported remotely is another question (I would have
added it to the IDL directly, but adding a dynamically loaded service
does not sound bad either)

Sylvain

2015-03-30 9:52 GMT-03:00 Janosch Machowinski <[email protected]>:
> Am 30.03.2015 um 14:48 schrieb Sylvain Joyeux:
>>>
>>> I don't plan to add an API to RTT itself. To keep RTT changes minimal,
>>> I aim at implement a Service, that adds an operation that does the
>>> query. The Service is supposed to be loaded remotely. (See my mail
>>> about that)
>>
>> Missing how that service accesses the information.
>>
>> Sylvain
>
> As the service adds a method to the Task, it then can access the
> connection manager of the ports. It is a local method then...
> One actually only needs a local pointer to a TaskContext to access
> the connection manager.
> 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