From owner-freebsd-hackers Fri Jan 16 20:45:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA01186 for hackers-outgoing; Fri, 16 Jan 1998 20:45:24 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from whizzo.TransSys.COM (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA01153 for ; Fri, 16 Jan 1998 20:45:03 -0800 (PST) (envelope-from louie@whizzo.TransSys.COM) Received: from whizzo.TransSys.COM (localhost.transsys.com [127.0.0.1]) by whizzo.TransSys.COM (8.8.8/8.7.3) with ESMTP id XAA09774; Fri, 16 Jan 1998 23:44:16 -0500 (EST) Message-Id: <199801170444.XAA09774@whizzo.TransSys.COM> X-Mailer: exmh version 2.0.1 12/23/97 To: daniel_sobral@voga.com.br cc: hackers@FreeBSD.ORG From: "Louis A. Mamakos" Subject: Re: Wide characters on tcp connections References: <8325658A.005211D4.00@papagaio.voga.com.br> In-reply-to: Your message of "Mon, 12 Jan 1998 11:58:36 -0300." <8325658A.005211D4.00@papagaio.voga.com.br> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 16 Jan 1998 23:44:16 -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk TCP doesn't know or care from chararacters or other datatypes; it simply provides you a full-duplex reliable octet stream between two endpoints. You encode your characters, integers, floating point numbers, etc. as you see fit. This is similar to asking if the UNIX filesystem has provisions for storing "wide characters in files"; the FS doesn't care what's inside it's files. louie