Lines Matching refs:configuration

50 /** The configuration controller is responsible for the management of the
54     <li>The current configuration contains the set of currently active
56     <li>The requested configuration describes what the current configuration
57     should be.  The requested configuration is changed usually by calling
62     <p>When the two configurations differ then the current configuration is
63     updated eventually to reflect the requested configuration.  An update
66     <li>when the last pending request for configuration changes has been
69     <li>when the configuration manager it is unlocked after formerly being
73     <p>Requests for configuration changes are handled in a two step process:
75     <li>First the requested configuration is updated iteratively: Every
84     configuration is made.  These changes are broadcasted to registered
91     empty.  Until this point only the requested configuration has been
95     the current configuration (the one that comprises the actually active
96     resources) reflects the requested configuration.</p>
108     remain in the requested configuration.  Every time the configuration
109     controller updates its current configuration these resources are
112     <p>The configuration controller sends the following events:
116     active in the requested configuration.  The event is sent when the
117     configuration change request is executed, not when the
124     in the requested configuration.  The event is sent when the
125     configuration change request is executed that is created when for
131     the current configuration starts.</p>
132     <p>The requested configuration is available in the <member
137     the current configuration ends.</p>
138     <p>The requested configuration is
150     configuration is removed from the configuration.</p>
164         configuration changes are sent after this call returns.</p>
183         configuration changes are sent after this call returns.</p>
205     /** Lock the processing of configuration change requests.
210         configuration controller is locked while <member>lock()</member> was
215     /** Unlock the processing of configuration change requests.
217         <member>lock()</member> and the queue of configuration change
218         requests is not empty the configuration controller continues the
220         configuration will eventually being made.</p>
224     /** Explicitly request an update of the current configuration.
232     /** Return a copy of the requested configuration.
233         <p>Modifications to the returned configuration have no effect on the
238     /** Return a copy of the current configuration.
239         <p>Modifications to the returned configuration have no effect on the
244     /** Replace the requested configuration with the given configuration and
245         schedule an update of the current configuration.
249         given configuration can have other origins then these methods.</p>
250         <p>The given configuration is transformed into a list of of change
251         requests so that the resulting reqeusted configuration equals the
252         given configuration.  This has the advantage that not only the
253         resource activations and deactivations but all configuration
255         <p>Note that because of the configuration change notifications
257         resulting requested configuration can be different from the given
258         configuration.</p>
260             This typically is a configuration that was obtained with an