Xref: utzoo alt.bbs:308 comp.misc:4369
Path: utzoo!hoptoad!uunet!labrea!rutgers!mailrus!cornell!batcomputer!itsgw!imagine!pawl17.pawl.rpi.edu!fargo
From: fargo@pawl17.pawl.rpi.edu (Ethan M. Young)
Newsgroups: alt.bbs,comp.misc
Subject: Re: New Ideas in BBSes (No BS!)
Keywords: BBS Client Server Network NOMSDOS
Message-ID: <2070@imagine.PAWL.RPI.EDU>
Date: 13 Dec 88 01:26:14 GMT
References: <1217@cps3xx.UUCP> <2093@uokmax.UUCP> <2324@ddsw1.MCS.COM> <437@telly.UUCP> <1089@tank.uchicago.edu> <243@taniwha.UUCP> <11373@reed.UUCP>
Sender: news@imagine.PAWL.RPI.EDU
Reply-To: fargo@pawl17.pawl.rpi.edu (Ethan M. Young)
Distribution: na
Organization: RPI Public Access Workstation Lab - Troy, NY
Lines: 15

As to the subject of supporting glass TTY's and ASCII terminals:

Instead of being stuck supporting ONLY ASCII dumb terminals, nor instead of
relying heavily on specialized protocols, a good BBS should allow the user to
choose which system he/she wants depending on the user's terminal set-up.  If
the user is stuck with a measly Courier terminal, then give that user the sup-
port available for a Courier.  But, if the user just happens to have a 2000x
2000x24 bit color display running a terminal emulator to handle it, then you
shouldn't have to stick that guy with a Courier interface.  All this can be
made as simple as selecting a menu item, hitting a letter, etc. which says,
"Which terminal emulator can you support?  (C)ourier  (V)T-100  (A)NSI etc."

Thank you and happy hunting!     Internet: fargo@pawl.rpi.edu                       ____    [> SB <]                       fargo@{paraguay|uruguay}.acm.rpi.edo
   /__      -=>??<=-          Bitnet (??): usergac0@rpitsmts.bitnet
  /   ARGO : 3000 years of regression from the year 4990