QOSCCM 1.0 NO IDEA Avatar
  1. OMG Issue

QOSCCM_ — Interceptor specific registration

  • Key: QOSCCM_-20
  • Legacy Issue Number: 11703
  • Status: closed  
  • Source: THALES ( Olivier Hachet)
  • Summary:

    Interceptor specific registration:
    The section 8.7 mentions in a note that « Possible specific registration
    operation (e.g., register only for a specific facet) shall be investigated
    in FTF. In constraint environments, the need can be to register interceptors
    at operation level.
    In section 8.3.4 there is no means for interceptor registration on specific
    operation of facet. We propose to introduce the ability to specify a port
    name and an operation name in order to access easily to these data at
    implementation level. No registration interface modifications are needed
    here.
    As said in section 8.3.4.1 name attribute can be also used to order
    interceptors stored into a list. We suggest adding a priority attribute that
    should supply such need.

  • Reported: QOSCCM 1.0b2 — Fri, 30 Nov 2007 05:00 GMT
  • Disposition: Resolved — QOSCCM 1.0
  • Disposition Summary:

    We propose to introduce the ability to specify a port name and an operation name in order to access easily to these data at implementation level. No registration interface modifications are needed here.
    As said in section 8.3.4.1 name attribute can be also used to order interceptors stored into a list. An addition of a priority attribute that should supply such need.
    Improvement of existing ContainerInterceptor interface in order to allow interceptor registration at facet and operation level.

  • Updated: Fri, 6 Mar 2015 20:54 GMT