I see.
Say I’m using PdxWriter.writeString and then reading the string in C++ using 
PdxReader ::readString. Am I correct in assuming C++ will get the raw bytes 
without any decoding done?
Should I call PdxReader::readWideString to do additional decoding?
If I’m using gemfire with two C++ clients only it’s up to me to make sure I’m 
matching writeString with readString and writeWideString to readWideString?

Thanks in advance!

Cosmin

From: Dan Smith [mailto:[email protected]]
Sent: 11 April 2016 19:58
To: [email protected]
Subject: Re: Supported string encoding in PDX

Hi Cosmin,
Strings less than 64K are encoded as UTF-8. Larger strings with multi byte 
characters are encoded as UTF-16 for performance reasons related to computing 
the size of the serialized data.
-Dan

On Mon, Apr 11, 2016 at 12:47 AM, CREMARENCO Cosmin 
<[email protected]<mailto:[email protected]>> wrote:
Hello,

What is the supported string encoding when reading/writing a string using PDX?
I wasn’t able to find that info in the doc. Am I correct in assuming that’s 
UTF8?

Thanks!

Cosmin

*******************************

This e-mail contains information for the intended recipient only. It may 
contain proprietary material or confidential information. If you are not the 
intended recipient you are not authorised to distribute, copy or use this 
e-mail or any attachment to it. Murex cannot guarantee that it is virus free 
and accepts no responsibility for any loss or damage arising from its use. If 
you have received this e-mail in error please notify immediately the sender and 
delete the original email received, any attachments and all copies from your 
system.

*******************************

This e-mail contains information for the intended recipient only. It may 
contain proprietary material or confidential information. If you are not the 
intended recipient you are not authorised to distribute, copy or use this 
e-mail or any attachment to it. Murex cannot guarantee that it is virus free 
and accepts no responsibility for any loss or damage arising from its use. If 
you have received this e-mail in error please notify immediately the sender and 
delete the original email received, any attachments and all copies from your 
system.

Reply via email to