-
Key: CORBA34-15
-
Legacy Issue Number: 6050
-
Status: closed
-
Source: Oracle ( Andrew Piper)
-
Summary:
For codesets in encapsulations we have:
15.3.3 - codesets must be "explicitly defined"
Issue 4824 - "it is an error for a Service Context to depend on information that is not contained within the encapsulation to determine the codeset used within it"
But in 13.8 there is no prescribed way of "explicitly defining" the codeset.
Please, please can we simply define that the fallbacks in 13.10.2.6 apply everywhere that the codeset is not known (whether negotiated or not) and be done with it.
Another alternative would be to add codeset parameters to the encode() and decode() functions of 13.8.
-
Reported: CORBA 3.0.2 — Tue, 26 Aug 2003 04:00 GMT
-
Disposition: Deferred — CORBA 3.4
-
Disposition Summary:
Deferred
This proposal was generated automatically by request of the Task Force Chair Adam Mitz.
-
Updated: Wed, 1 Feb 2023 21:58 GMT
CORBA34 — 15.3.3 - codesets must be "explicitly defined"
- Key: CORBA34-15
- OMG Task Force: CORBA 3.4 RTF