You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@geode.apache.org by CREMARENCO Cosmin <Co...@murex.com> on 2016/04/11 09:47:45 UTC
Supported string encoding in PDX
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.
Re: Supported string encoding in PDX
Posted by Dan Smith <ds...@pivotal.io>.
I don't know much about the gemfire native client - that's not actually
part of geode yet BTW. But I think the serialized PDX format itself ought
to be independent of which method is called because at the end of the day
if a java client client calls readString it should get a java String back,
and the java client only handles the format I described earlier.
-Dan
On Tue, Apr 12, 2016 at 12:55 AM, CREMARENCO Cosmin <
Cosmin.CREMARENCO@murex.com> wrote:
> 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:dsmith@pivotal.io]
> *Sent:* 11 April 2016 19:58
> *To:* user@geode.incubator.apache.org
> *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 <
> Cosmin.CREMARENCO@murex.com> 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.
>
RE: Supported string encoding in PDX
Posted by CREMARENCO Cosmin <Co...@murex.com>.
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:dsmith@pivotal.io]
Sent: 11 April 2016 19:58
To: user@geode.incubator.apache.org
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 <Co...@murex.com>> 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.
Re: Supported string encoding in PDX
Posted by Dan Smith <ds...@pivotal.io>.
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 <
Cosmin.CREMARENCO@murex.com> 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.
>