- 
                            Key: CORBA26-29
- 
                            Legacy Issue Number: 3725
- 
                            Status: closed
- 
                            Source: Laboratoire d`Informatique Fondamentale de Lille ( Raphael Marvie)
- 
                            Summary:When a component type is implemented, it inherits a specialized 
 interface for callback functions, for example SessionComponent. In
 this context, why should home implementations be unspecialized? Using
 a specific home type, deployment could be improved when performed in a
 multi-actor context. As the cooperation between containers and homes
 is unspecified, using multi-actors components seems unreachable. One
 particular aspect is how the container <Context> interface si provided
 to the component instance. Using a well defined specialized home
 interface would solve this problem easily. Thus, avoiding the use of
 wrappers for example which are another solution, but far more complex.
 Such an interface should be defined for each component type category.As an example the following interface could be a basis for session 
 component homes. (there must be other operations to add here, but I
 have not foudn them yet.)interface SessionCCMHome : CCMHome { // or CCMHomeKeyless void set_session_context ( in SessionContext sc ) ; }; 
- 
                            Reported: CPP 1.1 — Mon, 26 Jun 2000 04:00 GMT
- 
                            Disposition: Resolved — CORBA 2.6.1
- 
                            Disposition Summary:rejected 
- 
                            Updated: Fri, 6 Mar 2015 20:58 GMT
CORBA26 — Issue On the use of typed home (or CCMHome subtypes)
- Key: CORBA26-29
- OMG Task Force: Core RTF