Enhancement #1548
Transports returned by ParticipantConfig::getTransports() should be mutable
Status: | New | Start date: | 06/25/2013 | |
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assignee: | - | % Done: | 0% | |
Category: | C++ | |||
Target version: | rsb-0.18 |
Description
ParticipantConfig::getTransports()
returns a std::set
of deep-copied ParticipantConfig::Transport
objects. As elements of a std::set
, these objects are immutable which prevents the idiom
std::set<ParticipantConfig::Transport> transports = config.getTransports()
// modify transports
config.setTransports(transports);
History
#1 Updated by J. Wienke almost 11 years ago
I don't think this is easily possible, because internally we manage a map from name to transport class for checking duplicated transports. Exposing this map sounds dangerous to me and too complicated for the user.
However, the whole assumption that a single transport must appear only a single time might be wrong already. It could be perfectly valid to have two distinct socket transports running on different ports. I don't know how we should proceed here.
#2 Updated by J. Moringen over 10 years ago
- Target version changed from rsb-0.10 to rsb-0.11
#3 Updated by J. Wienke over 9 years ago
- Target version changed from rsb-0.11 to rsb-0.12
#4 Updated by J. Wienke about 9 years ago
- Target version changed from rsb-0.12 to rsb-0.13
#5 Updated by J. Moringen over 8 years ago
- Target version changed from rsb-0.13 to rsb-0.14
#6 Updated by J. Moringen about 8 years ago
- Target version changed from rsb-0.14 to rsb-0.15
#7 Updated by J. Moringen over 7 years ago
- Target version changed from rsb-0.15 to rsb-0.16
#8 Updated by J. Moringen about 7 years ago
- Target version changed from rsb-0.16 to rsb-0.17
#9 Updated by J. Moringen over 6 years ago
- Target version changed from rsb-0.17 to rsb-0.18