Services.idl ...

We also use Services.idl to get log messages from the server. This also
leads me to another question: does the KTaskBrowser will be updated
according to RTT 2.0 ?

2010/8/19 Sylvain Joyeux <sylvain [dot] joyeux [..] ...>

> Peter mentioned on a merge request on gitorious that Services.idl is
> obsolete.
>
> Now comes the question: how do I get the same functionality ??? Namely,
> stopping the RunOrb method from CORBA.
>
> Sylvain
> --
> Orocos-Dev mailing list
> Orocos-Dev [..] ...
> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-dev
>

Services.idl ...

On Thu, Aug 19, 2010 at 3:04 PM, Philippe Hamelin
<philippe [dot] hamelin [..] ...> wrote:
> We also use Services.idl to get log messages from the server. This also
> leads me to another question: does the KTaskBrowser will be updated
> according to RTT 2.0 ?

That is not in my planning yet. Demand creates patches however :-)

Peter

Services.idl ...

On Thu, Aug 19, 2010 at 2:50 PM, Sylvain Joyeux <sylvain [dot] joyeux [..] ...> wrote:
> Peter mentioned on a merge request on gitorious that Services.idl is
> obsolete.

It has been removed from the IDL to see if anyone starts yelling since
it's easier to remover first and add later than the other way around.

>
> Now comes the question: how do I get the same functionality ??? Namely,
> stopping the RunOrb method from CORBA.

The 'standard' way would be to call:

CAnyArguments_var empty = new CAnyArguments();
CService_var corbaservice = proxy->getProvider("corbaservice");
Any_var ret = corbaservice->callOperation("shutdown", empty.in() );

With these notes: getProvider could/should be renamed to getService.
In Python, this would have been a one-liner...

The retrieval of log() lines is also an issue. As the 'generalist',
I'd prefer that this is a service too, where ret contains a new log
line each time, but I'm easily convinced to streamline the API if
there is a need for it.

Peter