Legacy Issue Number: 3403
Source: International Business Machines ( Russell Butek)
Portable interceptor implementations need access to the ORB. In order to
accomplish this, the ORB must be defined in IDL There are four
possibilities that have been opined:
1. Define the ORB as "native ORB;"
This puts the ORB into the IDL namespace. However, the ORB is still
described in PIDL. This doesn't really help us to remove PIDL, some folks
feel this is a misuse of native, but it would be sufficient for the
requirements of PI.
2. Define an IDL wrapper for the ORB, call it proxyORB for now.
proxyORB would contain exactly the same items that the PIDL ORB does, only
defined in pure IDL. Advantages: this is a migration step toward getting
rid of ORB PIDL if we encourage folks to use proxyORB rather than ORB.
Disadvantages: dual maintenance; lots of work - too much for this FTF?; I
don't think we know all the ramifications; where do you get a proxyORB?
from the ORB?
3. Make the leap and redefine ORB in IDL now.
This option is similar to option 2, but the IDL is not a wrapper, it's the
real ORB. Advantages: no dual maintenance; we get rid of ORB PIDL right
now. Disadvantages: BIG step - too big for this FTF?; lots of work; I
don't think we know all the ramifications.
4. Make the ORB a primitive type like TypeCode.
This seems to be generally undesired. It requires all compilers to change.
Unless someone really likes this approach, I don't think we should even
Reported: CPP 1.1 — Thu, 16 Mar 2000 05:00 GMT
Disposition: Resolved — CORBA 3.0.2
Resolve this issue simultaneously with 3772 and close it as soon as 3772 is resolved and closed
Updated: Fri, 6 Mar 2015 20:58 GMT
CORBA3 — PI needs the ORB to be available in IDL
- Key: CORBA3-8
- OMG Task Force: Core 2002 RTF