Meetings2012-02-16 » History » Version 10
J. Moringen, 02/16/2012 05:06 PM
| 1 | 1 | J. Moringen | h1. Meetings 2012-02-16 |
|---|---|---|---|
| 2 | 1 | J. Moringen | |
| 3 | 1 | J. Moringen | h2. Configuration Service |
| 4 | 1 | J. Moringen | |
| 5 | 2 | J. Moringen | h3. Nomenclature |
| 6 | 2 | J. Moringen | |
| 7 | 7 | J. Moringen | * Configuration (Framework level) |
| 8 | 7 | J. Moringen | ** Converter [implemented] |
| 9 | 7 | J. Moringen | ** Transports (+ quality of service) [implemented] |
| 10 | 7 | J. Moringen | ** Error handling [implemented] |
| 11 | 8 | J. Moringen | ** (Renaming of) scope names [not implemented] |
| 12 | 7 | J. Moringen | *** Are these renaming rules, which are applied at participant creation time? |
| 13 | 7 | J. Moringen | *** Do they affect scopes or participants? |
| 14 | 9 | J. Moringen | * Parameter Service (Domain level) |
| 15 | 9 | J. Moringen | ** Component parameters |
| 16 | 9 | J. Moringen | *** Component-specific configuration has to be possible |
| 17 | 9 | J. Moringen | *** Changable at runtime? |
| 18 | 2 | J. Moringen | |
| 19 | 1 | J. Moringen | h3. Requirements |
| 20 | 2 | J. Moringen | |
| 21 | 4 | J. Moringen | * Remapping of scope names |
| 22 | 4 | J. Moringen | ** Remapping on the program-level is sufficient (i.e. participant level is not needed) |
| 23 | 1 | J. Moringen | ** Recursive renaming has be possible |
| 24 | 10 | J. Moringen | ** The remapping mechanism is applied when participants are instantiated |
| 25 | 5 | J. Moringen | ** Look at ROS's approach |
| 26 | 1 | J. Moringen | |
| 27 | 5 | J. Moringen | * Configuration mechanism has to be suitable for component layer (e.g. CCA) |