[Rock-dev] RTT InputPort: Enforce buffered connections for input ports
Martin Zenzes
martin.zenzes at dfki.de
Thu Jan 16 15:46:13 CET 2014
On 01/16/2014 02:31 PM, Sylvain Joyeux wrote:
> On 01/16/2014 01:01 PM, Martin Zenzes wrote:
>> Hi,
>>
>> is there a way to enforce a buffered connection for an input port (or a
>> connection between two certain modules, for that matter) of a orogen
>> module? I found the orogen statement "needs_buffered_connection", but am
>> a little bit lost concerning it's effects (none observed)
> This is only used as a hint. There are no reasons anymore to force the
> use of a buffered connection, as the choice of connection type is a
> matter of deployment (two different deployment choices can lead to two
> different connection policy choices), not component design.
Hm... So more a political thing ;-)
In my case (serial messages from many devicesincoming on one
port)throwing away messages does not make that much sense.
At least printing a warning in the startHook()?
The subtle errors on not using a buffered connection (all messages are
still valid, but some messages are lost) can be detected by looking at
the ndlcom-packet-counter at runtime...
More information about the Rock-dev
mailing list