Re: Updated dataflow semantics for RTT

Sylvain Joyeux <[email protected]> Fri, 25 Sep 2015 13:24:06 -0300

Newsgroups	gmane.science.robotics.orocos.devel
Message-ID	<CAFENT7JuBZV++S1RtzXbmoFUiKMxCFs2VVXCii3jc2rDZ=oevw@mail.gmail.com>

Hi Johannes

> To me, this calls for having different behaviours for data object and
> buffer objects: one data object per input port and one buffer per
> channel. In all cases. It would actually both fix the bug you describe
> above *and* keep mixed-policy behaviour as well as keep buffer setup
> feasible (since sizing buffers is meaningful only on a per-connection
> basis).

I did not get any comment from you about this ... It concerns me as my
current understanding is that by fixing RTT for your use case, you
would basically fundamentally break it for mine ...

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