Bug 465

Summary: Locality constrained objects and footprint reduction
Product: TAO Reporter: Carlos O'Ryan <coryan>
Component: ORBAssignee: Nanbor Wang <nanbor>
Status: RESOLVED FIXED    
Severity: enhancement    
Priority: P2    
Version: 1.0.14   
Hardware: All   
OS: All   
Bug Depends on:    
Bug Blocks: 118, 322, 451    

Description Carlos O'Ryan 2000-02-27 16:50:41 CST 
The CORBA Component Model has finally clarified the semantics of locality
constrained objects.  My understanding is that the objects do *not*
require a Servant, and are directly implemented by the proxy.  In fact,
a locality constrained object is only accessible as long as there is
an object reference for it.
This is related to the library footprint because currently TAO implements
locality constrained objects using separate servants and object references,
reducing the number of classes would reduce the code size.  It will also
reduce coupling in the library, as clients would not need to link the servant
base code (and carry a good chunk of the POA with them).
Comment 1 Carlos O'Ryan 2000-02-27 16:52:59 CST 
The questions raised by bug #118 are answered by the CCM spec.
Comment 2 Carlos O'Ryan 2000-02-27 16:54:59 CST 
Re-implementing the locality constrained objects based on the new CCM  should
decrease coupling in the library, and it is an important step to solve bug #451
Comment 3 levine 2000-03-05 09:29:59 CST 
Yours?
Comment 4 Nanbor Wang 2000-03-05 22:00:59 CST 
x.
Comment 5 Nanbor Wang 2000-03-27 13:41:59 CST 
I'll be working on this soon.
Comment 6 Nanbor Wang 2000-03-27 14:25:59 CST 
1
Comment 7 Nanbor Wang 2000-04-26 14:37:59 CDT 
The change is in and I'll deal with problems related to it in other places.