From owner-freebsd-hackers Tue Jan 20 02:43:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA24479 for hackers-outgoing; Tue, 20 Jan 1998 02:43:57 -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 CAA24467 for ; Tue, 20 Jan 1998 02:43:38 -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 IAA15708; Tue, 20 Jan 1998 08:43:25 -0200 Received: by papagaio.voga.com.br(Lotus SMTP MTA v1.06 (346.7 3-18-1997)) id 03256592.004062EA ; Tue, 20 Jan 1998 08:43:16 -0300 X-Lotus-FromDomain: VOGA To: louie@TransSys.COM cc: hackers@FreeBSD.ORG Message-ID: <83256592.0040388D.00@papagaio.voga.com.br> Date: Tue, 20 Jan 1998 08:43:10 -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 > the issue is "awareness" of the underlying {transport, > storage} mechansim. > There's really no point in reimplementing a transport > protocol given the literally thousands of man-hours of > work by a lot of clever people over more than a decade > to make TCP work well. As far as my question goes, that was not the issue. The issue is the existance, or not, standards for transporting wide characters over TCP, in a higher layer. -- Daniel C. Sobral (8-DCS) Daniel_Sobral@voga.com.br Tagline: * FreeBSD. Earth.