Date: Tue, 20 Jan 1998 15:15:58 +1100 (EST) From: Andrew Kenneth Milton <akm@mother.sneaker.net.au> To: louie@TransSys.COM (Louis A. Mamakos) Cc: daniel_sobral@voga.com.br, hackers@FreeBSD.ORG Subject: Re: Wide characters on tcp connections Message-ID: <199801200415.PAA17887@mother.sneaker.net.au> In-Reply-To: <199801200240.VAA20667@whizzo.TransSys.COM> from "Louis A. Mamakos" at Jan 19, 98 09:40:32 pm
next in thread | previous in thread | raw e-mail | index | archive | help
+-----[ Louis A. Mamakos ]------------------------------
|
|
| > Though that's technically right, one might feel the need for a standard if
| > the files he writes are going to be read by other people's programs. Of
| > course TCP, by itself, provides all support you need to send the
| > characters, but ignoring the practical problems would be akin to keeping to
| > IP (vs TCP or UDP) because that's all you _really_ need...
|
| What? While you might agree to implement your own transport protocol
| directly on IP or using UDP to do multiplexing with your own reliable
| transport, none of this makes it any easier to move multibyte characters
| between machines.
|
| If you're looking for a standard way to move multibyte characters, then
| choose any one of a number of encodings already used to store multibyte
| characters in files.
Moving them's not quite the same as storing them.... byte orders, usually
come into play a lot more when you've got to shunt the data across a network.
I think Unicode defines that it is to be stored in network byte order.
Although how standard is your wchar_t between platforms? See another thread
for the answer to that one.
Your best bet is a higher level (more expensive) wrapping like XDR so
that you know that you can transport it between platforms. Or roll your
own.
--
,-_|\ SneakerNet | Andrew Milton | GSM: +61(41)6 022 411
/ \ P.O. Box 154 | akm@sneaker.net.au | Fax: +61(2) 9746 8233
\_,-._/ N Strathfield +--+----------------------+---+ Ph: +61(2) 9746 8233
v NSW 2137 | Low cost Internet Solutions |
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199801200415.PAA17887>