QOSCCM_ — Configuration of the underlying middleware

Configuration of the underlying middleware:
The « three different realization mecanisms » mentionned in section 1.1 are
not all managed in the specification. Especially the second topic « The
configuration of the underlying middleware, for instance the use of certain
policies of the portable object adapter, or object references, typically in
order for QoS properties to be propagated in a suitable way ».
Interceptor mechanism allows injection of non-functional properties at
interception points, but it is not sufficient to correlate non-functional
properties with component feature out of the calling process. The necessity
to configure the underlying middleware, for instance the use of certain
policies of the portable object adapter, or object references, may be
designed with new interfaces as well as interceptors.
We propose to introduce a means to configure on activation interception
points to configure POA or RT-POA policies on the activation of a facet.
This shall also allow to have "on connection interception" to set easily the
transport protocol policies (SHMIOP, UIOP,...)

We propose to introduce a means to configure on activation interception points to configure POA or RT-POA policies on the activation of a facet. This shall also allow to have "on connection interception" to set easily the transport protocol policies (SHMIOP, UIOP,...).
We propose to add a means to configure the underlying middleware corresponding to the second mechanisms mentioned in section 1.1. This one is not managed by the specification.
Below a section to be added after Negotiation is presented. The mechanism is designed with new interfaces as well as interceptor mechanism.