I am not sure, but your idea seems somehow similar to the ?-calculus:

http://en.wikipedia.org/wiki/Pi-calculus

Piotr.

On Tue, Jun 7, 2011 at 10:52, Willy Lambert <lambert [dot] willy [..] ...> wrote:

> Hi all,
>
> this is a crazy question but it is possible (and does it will make sense)
> to send a (stopped) taskcontext througth a port ? Is it still possible on 2
> separated machines ? (I wonder about the component.so that won't necessarely
> be on the two machines
>
> --
> Orocos-Users mailing list
> Orocos-Users [..] ...
> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
>
>

On Tuesday 07 June 2011 10:52:19 Willy Lambert wrote:
> Hi all,
>
> this is a crazy question but it is possible (and does it will make sense)
> to send a (stopped) taskcontext througth a port ?

You can't send/copy the object itself through a port. This will crash horribly
as it keeps pointers to all kinds of other objects.

> Is it still possible on
> 2 separated machines ? (I wonder about the component.so that won't
> necessarely be on the two machines

What you could try is to send a TaskContext* pointer over a port, connected
with the CORBA transport. The Corba transport will convert it to a corba
object reference, send that over and the receiving side will receive a
TaskContext* pointing to a proxy for the original object.

I added this if users wanted to pass TaskContext* pointers in operation
arguments. But it could work on ports equally well (no extra code is
required).

I'm not sure if this is unit tested, so it might/will be bumpy :-)

Peter