Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sdd.hp.com!hplabs!pyramid!lstowell
From: lstowell@pyrnova.pyramid.com (Lon Stowell)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: LAT vs telnet
Message-ID: <154113@pyramid.pyramid.com>
Date: 2 May 91 18:30:09 GMT
Sender: daemon@pyramid.pyramid.com
Reply-To: lstowell@pyrnova.pyramid.com (Lon Stowell)
Organization: Pyramid Technology Corp., Mountain View, CA
Lines: 23

In article <1991May2.012159.23962@megadata.mega.oz.au> andrew@megadata.mega.oz.au (Andrew McRae) writes:
>
>Has anyone attempted to define or build a public domain LAT-style
>local terminal protocol? If DEC would loosen up on LAT, that would
>solve the problem, but is that likely?
>
    How about just adding a block or full screen mode option to
    Telnet?   tn3270 is somewhat what I mean, but not quite.

    User input would be edited, parsed, etc. at the entry point,
    then forwarded into the network only when an Enter key is
    pressed...or a Function key.   

    Unfortunately then you would have to teach all the Unix
    programmers how to deal with REAL terminals rather than
    keystrokes.. >:-)

    No real reason why this would be a local terminal only, a
    decent "routable" block mode terminal transport would do a
    lot to reduce LAN/WAN congestion.

    (Yeah, I know, put 3270 datastreams in IP
    packets....blechhh.)