Bug 3528 - Add GIOP 1.4 support which has other behaviour for ucs2/ucs4
Summary: Add GIOP 1.4 support which has other behaviour for ucs2/ucs4
Status: NEW
Alias: None
Product: TAO
Classification: Unclassified
Component: ORB (show other bugs)
Version: 1.6.6
Hardware: All Windows NT
: P3 enhancement
Assignee: DOC Center Support List (internal)
URL:
Depends on:
Blocks:
 
Reported: 2008-12-08 16:52 CST by Johnny Willemsen
Modified: 2013-08-12 07:15 CDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Johnny Willemsen 2008-12-08 16:52:18 CST 
For GIOP 1.1, 1.2, and 1.3, UCS-2 and UCS-4 should be encoded using the endianess of the GIOP message, for backward
compatibility.
For GIOP 1.4, the byte order rules for UCS-2 and UCS-4 are the same as for UTF-16.
UTF-16LE and UTF-16BE, from IANA codeset registry, have their own endianess definition. Thus these should be
encoded using the endianess specified by their endianness definition.
Comment 1 Johnny Willemsen 2013-08-12 07:15:08 CDT 
GIOP 1.3 extends what is legal when using typecode indirection, this is not supported in TAO also