From owner-freebsd-hackers Wed Jan 21 02:50:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA12694 for hackers-outgoing; Wed, 21 Jan 1998 02:50:36 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from db2server.voga.com.br (db2server.voga.com.br [200.239.39.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA12679 for ; Wed, 21 Jan 1998 02:50:14 -0800 (PST) (envelope-from daniel_sobral@voga.com.br) From: daniel_sobral@voga.com.br Received: from papagaio.voga.com.br (papagaio.voga.com.br [200.239.39.2]) by db2server.voga.com.br (8.8.3+2.6Wbeta9/8.8.7) with SMTP id IAA15286; Wed, 21 Jan 1998 08:47:11 -0200 Received: by papagaio.voga.com.br(Lotus SMTP MTA v1.06 (346.7 3-18-1997)) id 03256593.0040BC63 ; Wed, 21 Jan 1998 08:47:05 -0300 X-Lotus-FromDomain: VOGA To: louie@TransSys.COM cc: hackers@FreeBSD.ORG Message-ID: <83256593.00404817.00@papagaio.voga.com.br> Date: Wed, 21 Jan 1998 08:46:59 -0300 Subject: Re: Wide characters on tcp connections Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk > My comment was in response to the original poster's remark > that if TCP wasn't going to do this, then was it a better > idea to implement a scheme using UDP or directly over IP. You completely misread my remark. I said that not dealing with wide character issues because they can be sent as bytes in a tcp stream would be the same as not implementing tcp at all because you can resort to ip. Why use TCP if IP provides everything you need? Because TCP is a standard way of doing a common kind of connection. Now, TCP goes _over_ IP. My question is similar to "how do I provide over IP connections?" The answer would be "use tcp". Well, I'm asking how do I send wide characters over tcp connections? -- Daniel C. Sobral (8-DCS) Daniel_Sobral@voga.com.br Tagline: * FreeBSD. Earth.