On 05/07/2010 02:36 AM, Gordon Sim wrote:
On 05/06/2010 11:27 PM, Rafael Schloming wrote:
What I was saying above is that I don't think the C++ API will
automatically decode the raw bytes into a wide string for you, but it
has to at least give you enough information to do that yourself,
otherwise it is essentially throwing information away and won't
interoperate correctly.
Indeed, and it does. There is an encoding specified on Variant. This
will be set when reading from the wire, and can be used when writing
to indicate the encoding the data is in.
Encoding is a string.
In Codecs.cpp, it seems to use strings that represent ISO 8859-15,
UTF-8, and UTF-16. Are these the formats that we support?
When writing to a message, is it set to UTF-16 for Python and Java
clients? What determines the setting for C++ clients?
When reading from a message, is it set to UTF-16 for Python and Java
clients, with automatic conversion if these other formats are used? When
reading from a message, I think you are saying that a C++ client should
check the encoding and take it into account when reading the string.
Did I get that right?
Jonathan
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
