-
Key: SEC17-5
-
Legacy Issue Number: 2708
-
Status: closed
-
Source: University of California, Irvine ( Carlos O'Ryan)
-
Summary:
Minor full_desc: The 2.2 spec states: "The hexadecimal strings are generated by first turning an object reference into
an IOR, and then encapsulating the IOR using the encoding rules of CDR." but it does not state which codeset is used in that
CDR encoding, since IIOP profiles contain strings (the hostname) the choice of codeset is crucial for interoperability Though most
implementors will probably use ASCII (UTF8) for that encoding a clarification seems to be required. -
Reported: SEC 1.6 — Tue, 8 Jun 1999 04:00 GMT
-
Disposition: Resolved — SEC 1.7
-
Disposition Summary:
to Close with agreed change
-
Updated: Sat, 7 Mar 2015 09:03 GMT