-
Key: QOSCCM_-5
-
Legacy Issue Number: 9740
-
Status: closed
-
Source: Fraunhofer FOKUS ( Tom Ritter)
-
Summary:
This needs clarification. Does each COPI get its own slot_id assigned by the container? Does the COPI control what (if anything) goes in this slot?
-
Reported: QOSCCM 1.0b2 — Thu, 18 May 2006 04:00 GMT
-
Disposition: Resolved — QOSCCM 1.0
-
Disposition Summary:
The usage of the slot id needs more detailed specification to be used in an
interoperable way. The following text will be given in response to this issue:
COPIs are not able to allocate a slot id since this is done in the ORBInitializer
which is executed at component server creation, which is before any user code
(i.e. COPI) is executed. Therefore, a slot id is allocated by the component server
and is communicated to the COPI by using the set_slot_id method. By using this
slot_id Container Portable Interceptors can have access to a PICurrent slot to
exchange thread and call specific information. All COPIs get the same slot id
since the number of registered COPIs is not known beforehand. A definition of
the content of the slot where COPIS can read and add information is also added -
Updated: Fri, 6 Mar 2015 20:54 GMT