Bug #2043

semantic of ParticipantConfig::setTransports not conform to doc/name

Added by R. Haschke over 8 years ago. Updated almost 8 years ago.

Status:ResolvedStart date:10/07/2014
Priority:NormalDue date:
Assignee:J. Wienke% Done:


Target version:rsb-0.13


current implementation of ParticipantConfig::setTransports actually only adds new transports,
but neither removes existing ones nor reconfigures existing ones.

From function name and doc, I would expect that setTransports does

this->transports.swap (arg)

i.e. replaces the existing set of transports with the new one.

Associated revisions

Revision 27feeda9
Added by J. Wienke almost 8 years ago

ParticipantConfig::setTransports: replace everything

Instead of adding only non-existing transports, make the semantics
clearer and completely replace all transport configurations in

fixes #2043


#1 Updated by J. Wienke almost 8 years ago

  • Category set to C++
  • Status changed from New to In Progress
  • Assignee set to J. Wienke
  • Target version set to rsb-0.13

#2 Updated by J. Wienke almost 8 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 0 to 100

Also available in: Atom PDF