----- Original Message ----- From: "Arno Garrels" <[EMAIL PROTECTED]> To: "ICS support mailing" <twsocket@elists.org> Sent: Monday, December 01, 2008 4:04 PM Subject: Re: [twsocket] D2009 does not recognize TSslHttpCli
> > So UnicodeString is your only choice and UTF-8 would be the prefered > encoding for data exchange. > >> It is sent in the url. > > URLs have to be UTF-8 and URL encoded so no problemo. I changed URL > encoding recently to UTF-8. However all URL functions take a String and > return a String, that is a UnicodeString in D2009, this is possible since > the > URL encoded string only contains characters from the ASCII printable > range. > So when the URL encoded UnicodeString is sent it can be converted to > ANSI with any current code page without data loss. > >> Difficult to test here.. > > You can write a small test application and see how it works. > I've been testing with it, but the server answers in a stream which is actually an ansistring in a stream. To decode it properly, I have to use an ansistring also (tested) Paul -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
