Enhancement #216
Externalize creation of transport objects in client-level code
| Status: | Resolved | Start date: | 02/25/2011 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | J. Moringen | % Done: | 100% | |
| Category: | C++ | |||
| Target version: | - |
Description
Currently Publishers and Subscribers create their own instances of Router, the router in turn creates his own instance of Ports etc. A better rapproach would be to manually pass them in the constructor of this classes. This enhances the testability of single classes and avoids passing configuration strings to the TransportFactory. Ideally this is the task of an RsbFactory.
Related issues
History
#1 Updated by J. Wienke about 13 years ago
- Assignee changed from S. Wrede to J. Moringen
We decided to orchestrate the creation of this objects and passing them to others in rsb::Factory.
Jan, this is probably related to your changes while separating in and out routes?
#2 Updated by J. Moringen about 13 years ago
- Status changed from New to Resolved
- % Done changed from 0 to 100