Re: [twsocket] ClientCnx.AnswerString

2009-01-10 Thread Arno Garrels
Arno Garrels wrote: Maybe an overload that takes the code page suits better, since AnswerString is virtual? > Paul wrote: > >> It's mostly ascii characters, but sometimes, the string contains a >> few unicode characters which can have different code pages for each >> character. Since the Clien

Re: [twsocket] ClientCnx.AnswerString

2009-01-09 Thread Arno Garrels
Paul wrote: > It's mostly ascii characters, but sometimes, the string contains a few > unicode characters which can have different code pages for each > character. Since the ClientCnx.AnswerString is an AnsiString anyway, > I think the only choise is to convert them to UTF8. That's correct, howe

Re: [twsocket] ClientCnx.AnswerString

2009-01-09 Thread Paul
quot;ICS support mailing" Sent: Friday, January 09, 2009 7:09 PM Subject: Re: [twsocket] ClientCnx.AnswerString > Unicode is IMHO valid, it depends on the content-type charset. > Should be "utf-16" for UnicodecodeString. > But in the wild I never saw a utf-16 header so far,

Re: [twsocket] ClientCnx.AnswerString

2009-01-09 Thread Arno Garrels
Paul wrote: > Are unicode characters in the body part not conform the RFC then ? Unicode is IMHO valid, it depends on the content-type charset. Should be "utf-16" for UnicodecodeString. But in the wild I never saw a utf-16 header so far, probably since it's a wast of bandwith sending double byte c

Re: [twsocket] ClientCnx.AnswerString

2009-01-09 Thread Paul
--- Original Message - >> From: "Paul" >> To: "TWsocket" >> Sent: Friday, January 09, 2009 3:26 PM >> Subject: [twsocket] ClientCnx.AnswerString >> >> >>> Is this still an AnsiString (httpCli) ? >>> I'm converting a

Re: [twsocket] ClientCnx.AnswerString

2009-01-09 Thread Arno Garrels
ing). Most likely an additional code page parameter won't hurt. -- Arno Garrels [TeamICS] http://www.overbyte.be/eng/overbyte/teamics.html > > Paul > > > - Original Message - > From: "Paul" > To: "TWsocket" > Sent: Friday, January

Re: [twsocket] ClientCnx.AnswerString

2009-01-09 Thread Paul
Forgot to add : it's sent in the body part of ClientCnx.AnswerString on the server Paul - Original Message - From: "Paul" To: "TWsocket" Sent: Friday, January 09, 2009 3:26 PM Subject: [twsocket] ClientCnx.AnswerString > Is this still an AnsiString (h

[twsocket] ClientCnx.AnswerString

2009-01-09 Thread Paul
Is this still an AnsiString (httpCli) ? I'm converting a few applications to D2009, but it seems I still have to use an AnsiString on the client side to read it the reply from the server. The server is compiled with D2009. regards, Paul -- To unsubscribe or change your settings for TWSocket m