[Rock-dev] [rock] #107: orocos.rb: connect_to behavior
rock
noreply at opendfki.de
Thu Feb 16 10:35:47 CET 2012
#107: orocos.rb: connect_to behavior
-------------------+-----------------------------------
Reporter: thro02 | Owner: rock-dev-mailing-list
Type: defect | Status: new
Priority: normal | Component: base
Keywords: |
-------------------+-----------------------------------
The current behavior of 'connect_to' allows to create multiple connections
between the same input and output port. This leads to a reading of a
corresponding number of NEW samples on the receiver side, when sending
only ONE item to the actual output port, e.g. using the following
(incomplete) example
sender.out.connect_to receiver.in
sender.out.connect_to receiver.in
sender.out.connect_to receiver.in
...
in receiver's Task.cpp updateHook
while(_in.read(sample) == RTT::NewData)
{
// When sender sends one sample on 'out' port
// three loops taken here, i.e. 1 per created connection
}
I intuitively would have expected a restriction of one connection per
input/output port.
Stumbled across this while using autoconnect and also establishing
connections manually in the supervision.
--
Ticket URL: <http://rock.opendfki.de/ticket/107>
rock <http://rock.opendfki.de>
rock: the robot construction kit
More information about the Rock-dev
mailing list