From owner-freebsd-current  Mon Jul 21 17:36:26 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id RAA23044
          for current-outgoing; Mon, 21 Jul 1997 17:36:26 -0700 (PDT)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50])
          by hub.freebsd.org (8.8.5/8.8.5) with SMTP id RAA23039
          for <current@FreeBSD.ORG>; Mon, 21 Jul 1997 17:36:23 -0700 (PDT)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id RAA12217; Mon, 21 Jul 1997 17:33:22 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199707220033.RAA12217@phaeton.artisoft.com>
Subject: Re: /usr/src/lib/libtelnet - why?
To: jkh@time.cdrom.com (Jordan K. Hubbard)
Date: Mon, 21 Jul 1997 17:33:22 -0700 (MST)
Cc: current@FreeBSD.ORG
In-Reply-To: <199707211610.JAA28312@time.cdrom.com> from "Jordan K. Hubbard" at Jul 21, 97 09:10:03 am
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

[ ... telnet protocol ... ]

>    1. There does not, it would appear, exist any reasonable API
>       and library for handling this kind of stuff, leaving the actual
>       UI details up a layer where you'd think they should be.  That
>       kinda sucks since anybody wanting to communicate over a socket
>       with telnet protocol (who's not telnet) has to reimplement this
>       all from scratch.

Look at the FTP code, specifically the control channel code, which
uses telnet protocol.  I did this same thing for a modem server
product in 1988.


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.