Re: Updated dataflow semantics for RTT

--===============1397777263==
Content-Type: multipart/alternative; boundary=001a11425fb4a59fd7052054ed30

--001a11425fb4a59fd7052054ed30
Content-Type: text/plain; charset=UTF-8

On Tue, Sep 22, 2015 at 1:48 PM, Sylvain Joyeux <[email protected]>
wrote:

> > push: Every input port has a single input buffer and all connected
> writers
> > write into that buffer.
>
> That still sounds very much like "shared" to me:
>
> > shared: Multiple input ports can read from the same buffer, so one read
> > operation can influence the outcome of another.
>

For private connections the buffer (or buffers in pull mode) belongs to a
single input port, which does not mean that it cannot be filled by multiple
writers (in push mode).
For shared connections multiple input ports read from the same buffer. So
the "shared" here is meant from the viewpoint of the input port ("I have my
own input buffer." vs. "I have to share my input buffer with other
readers."), not for output ports. Output ports may always serve multiple
connections/channels except in the shared pull mode ("I have a new sample
available and whoever polls me first will get it.").

Johannes


-- 
Johannes Meyer, Senior Application Engineer
+32 468 139828
Intermodalics - Kapeldreef 60, 3001 Heverlee - BELGIUM
www.intermodalics.eu

--001a11425fb4a59fd7052054ed30
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Tue, Sep 22, 2015 at 1:48 PM, Sylvain Joyeux <span dir=3D"ltr">&lt;<=
a href=3D"mailto:[email protected]" target=3D"_blank">sylvain.joyeux@m=
4x.org</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"=
margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=
=3D"">&gt; push: Every input port has a single input buffer and all connect=
ed writers<br>
&gt; write into that buffer.<br>
<br>
</span>That still sounds very much like &quot;shared&quot; to me:<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
&gt; shared: Multiple input ports can read from the same buffer, so one rea=
d<br>
&gt; operation can influence the outcome of another.<br></div></div></block=
quote><div><br></div><div>For private connections the buffer (or buffers in=
 pull mode) belongs to a single input port, which does not mean that it can=
not be filled by multiple writers (in push mode).<br></div><div>For shared =
connections multiple input ports read from the same buffer. So the &quot;sh=
ared&quot; here is meant from the viewpoint of the input port (&quot;I have=
 my own input buffer.&quot; vs. &quot;I have to share my input buffer with =
other readers.&quot;), not for output ports. Output ports may always serve =
multiple connections/channels except in the shared pull mode (&quot;I have =
a new sample available and whoever polls me first will get it.&quot;).</div=
><div><br></div><div>Johannes</div></div><br clear=3D"all"><div><br></div>-=
- <br><div class=3D"gmail_signature"><div dir=3D"ltr"><span style=3D"color:=
rgb(136,136,136)">Johannes Meyer, Senior Application Engineer</span><br><sp=
an><font color=3D"#888888">+32=C2=A0</font></span>468 139828<span><font col=
or=3D"#888888"><br>
Intermodalics - Kapeldreef 60, 3001 Heverlee - BELGIUM<br>
<a href=3D"http://www.intermodalics.eu" target=3D"_blank">www.intermodalics=
.eu</a></font></span></div></div>
</div></div>

--001a11425fb4a59fd7052054ed30--

--===============1397777263==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1397777263==--