-
Key: CORBA24-148
-
Legacy Issue Number: 3235
-
Status: closed
-
Source: Thematix Partners LLC ( Jishnu Mukerji [X] (Inactive))
-
Summary:
Part 2: Should an ORB be allowed to drop non-standard profiles (as it is allowed
to, indeed almost encouraged to do in GIOP/IIOP 1.2) even though it is not faced
with any resource contraints. Moreover, when it is faced with resource
contraints should it be required to follow a specific sequence in determining
what profiles to drop. -
Reported: CPP 1.1 — Tue, 18 Jan 2000 05:00 GMT
-
Disposition: Resolved — CORBA 2.4
-
Disposition Summary:
The proposed resolution defines two possible IOR conformance classes for every ORB interoperability
-
Updated: Fri, 6 Mar 2015 20:58 GMT
CORBA24 — Should an ORB be allowed to drop non-standard profiles
- Key: CORBA24-148
- OMG Task Force: CORBA Core 2.4 RTF