Meetings2012-02-16 » History » Version 8
Version 7 (J. Moringen, 02/16/2012 05:02 PM) → Version 8/15 (J. Moringen, 02/16/2012 05:02 PM)
h1. Meetings 2012-02-16
h2. Configuration Service
h3. Nomenclature
* Configuration (Framework level)
** Converter [implemented]
** Transports (+ quality of service) [implemented]
** Error handling [implemented]
** (Renaming **(Renaming of) scope names [not implemented]
*** Are these renaming rules, which are applied at participant creation time?
*** Do they affect scopes or participants?
* Parameter Service
** Domain level
*** Component parameters
**** Changable at runtime?
h3. Requirements
* Remapping of scope names
** Remapping on the program-level is sufficient (i.e. participant level is not needed)
** Recursive renaming has be possible
** Look at ROS's approach
* Configuration mechanism has to be suitable for component layer (e.g. CCA)
h2. Configuration Service
h3. Nomenclature
* Configuration (Framework level)
** Converter [implemented]
** Transports (+ quality of service) [implemented]
** Error handling [implemented]
** (Renaming **(Renaming of) scope names [not implemented]
*** Are these renaming rules, which are applied at participant creation time?
*** Do they affect scopes or participants?
* Parameter Service
** Domain level
*** Component parameters
**** Changable at runtime?
h3. Requirements
* Remapping of scope names
** Remapping on the program-level is sufficient (i.e. participant level is not needed)
** Recursive renaming has be possible
** Look at ROS's approach
* Configuration mechanism has to be suitable for component layer (e.g. CCA)