From owner-freebsd-net Mon May 15 12:59:23 2000 Delivered-To: freebsd-net@freebsd.org Received: from new1.utep.edu (new1.utep.edu [129.108.1.217]) by hub.freebsd.org (Postfix) with ESMTP id 779E837B658 for ; Mon, 15 May 2000 12:59:13 -0700 (PDT) (envelope-from jan@janbeck.com) Received: from mail.utep.edu (mail.utep.edu [129.108.1.4]) by new1.utep.edu (8.9.3/8.9.3) with ESMTP id NAA13404; Mon, 15 May 2000 13:59:01 -0600 (MDT) Received: from backup4 (atlas51.mmtlc.utep.edu [129.108.79.150]) by mail.utep.edu (8.9.2/8.9.2) with ESMTP id NAA106782; Mon, 15 May 2000 13:58:46 -0600 Message-Id: <4.2.0.58.20000515150136.00a5ba20@mail.janbeck.com> X-Sender: janbeck01@mail.janbeck.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Mon, 15 May 2000 15:01:58 -0500 To: Barney Wolff , freebsd-net@FreeBSD.ORG From: Jan Beck Subject: Re: socket programming In-Reply-To: <391ee6760.158e@databus.databus.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Thank you all for the info. I really appreciate the help JAn At 01:29 PM 5/14/00 -0400, Barney Wolff wrote: >Have you actually tried it, with a real telnet client? > >As I understood the question, it was: How does the server make the >client stop echoing to the user? And the answer is for the server >to tell the client that it will do the echoing itself, and then >not really do it. > >See RFC 857. > >Barney > > > Date: Sun, 14 May 2000 19:28:30 +0200 > > From: Alexander Langer > > To: Barney Wolff > > Cc: freebsd-net@FreeBSD.ORG > > Subject: Re: socket programming > > Content-Length: 660 > > > > Thus spake Barney Wolff (barney@databus.com): > > > > > Well, telnet is a funny protocol. Both answers have been wrong. > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > Interesting point. Unfortunately, since the server isn't going to echo > > back the chars, DON'T ECHO has the same effect. > > > > The difference between DON'T/WILL has effect if you assume, that the > > server echo's back each char it receives. Then client in WILL > > situation will echo, client in DON'T won't echo. But since the server > > won't echo anyways, there's no difference. > > > > You could have pointed that out without telling us we are wrong, which > > isn't true. > > > > Alex > > > > -- > > I need a new ~/.sig. > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-net" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message