History

Meetings2012-02-16 » History » Version 5

Version 4 (J. Moringen, 02/16/2012 04:59 PM) → Version 5/15 (J. Moringen, 02/16/2012 05:00 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 of) scope Scope names [not implemented]
**** Are these renaming rules, which are applied at participant creation time?
**** Do they affect scopes or participants?
** Domain level
*** Component parameters
**** Changable at runtime?

* Parameter Service?

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 must be suitable for component layer (e.g. CCA)