Re: Format of string output of a socket server
- From: "Alexander Nickolov" <agnickolov@xxxxxxxx>
- Date: Tue, 3 Oct 2006 12:09:02 -0700
UNICODE is the only sane choice of course. However, don't
confuse with the Windows meaning of UNICODE which is
really only the UTF-16 representation of UNICODE. I'd
suggest you use UTF-8 representation of UNICODE to avoid
byte-ordering issues on the network. What you return to
your clients is up to you - you just need to do the appropriate
format conversion (e.g. MultiByteToWideChar to get UTF-16
for example).
--
=====================================
Alexander Nickolov
Microsoft MVP [VC], MCSD
email: agnickolov@xxxxxxxx
MVP VC FAQ: http://www.mvps.org/vcfaq
=====================================
"Angus" <nospam@xxxxxxxxx> wrote in message
news:eXxFh8m5GHA.400@xxxxxxxxxxxxxxxxxxxxxxx
Hello
I am writing a socket server to deliver telephony events to clients on a
network. For example the telephony server might send out text to
connected
clients. Clients might be written in C/C++, Java, Visual Basic, anything
in
fact which can talk to a socket.
My socket server is currently sending out char* . Do I have to worry
about
the format of string output? Should I be outputting Unicode? Some other
format? Or would a C/C++ char* be OK? Will eg Java understand it? Do
they
use UTF-8 or something?
Angus
.
- Follow-Ups:
- Re: Format of string output of a socket server
- From: Angus
- Re: Format of string output of a socket server
- References:
- Format of string output of a socket server
- From: Angus
- Format of string output of a socket server
- Prev by Date: Re: Server question - how to send data to particular socket
- Next by Date: how to bind to a remote machine?
- Previous by thread: Re: Format of string output of a socket server
- Next by thread: Re: Format of string output of a socket server
- Index(es):
Relevant Pages
|
Loading
