From owner-freebsd-hackers Mon Jan 12 05:58:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA10744 for hackers-outgoing; Mon, 12 Jan 1998 05:58:11 -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.7/8.8.7) with ESMTP id FAA10658 for ; Mon, 12 Jan 1998 05:57:57 -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 LAA11728 for ; Mon, 12 Jan 1998 11:58:49 -0200 Received: by papagaio.voga.com.br(Lotus SMTP MTA v1.06 (346.7 3-18-1997)) id 0325658A.005245FE ; Mon, 12 Jan 1998 11:58:38 -0300 X-Lotus-FromDomain: VOGA To: hackers@FreeBSD.ORG Message-ID: <8325658A.005211D4.00@papagaio.voga.com.br> Date: Mon, 12 Jan 1998 11:58:36 -0300 Subject: Wide characters on tcp connections Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk I know this list may not be adequate for this question, but AFAIK, no list is. I'd like to know if there is any provision on TCP protocol for wide-character tcp streams. Feel free to answer privately if you find this too off-topic. -- Daniel C. Sobral (8-DCS) Daniel_Sobral@voga.com.br