🚀 go-pugleaf

>From Zellich@OFFICE-3 Mon Jul 13 04:50:39 1981
Some of us already *do* work at home, and the receipt of stuff
that shows up in my office inbasket is a problem -- I have to
go in and get it periodically, or else have it batch-mailed to
me (the Post Awful actually does pretty good work here - I get
everything the next day).

At home I have a pretty nice workstation, but on a recent
vacation trip I took a TI745 with me, and found it not nearly
as useful as it had been when it was my *only* terminal.  My
work methodology has changed so much due to the availability
of the workstation that it has become almost impossible to
get my work done with a terminal with lesser capabilities.
My electronic "filing cabinets", etc., are optimally organized
for a windowed display, and have become extremely difficult to
use from a TTY or simple scope.

It so happens that my workstation is relatively dumb (using
its internal microprocessor to handle NVT requirements only),
but the next generation should be quite intelligent - maybe
being my prime "host" itself.  This all points up two problems
very neatly:

  1.  I need a portable workstation (or portable terminal that
      can access my workstation);

  2.  If I use a portable terminal, then I need access to my
      home workstation (the future one, that will be a
      standalone system).  This future system must be capable
      of two-way communication; it can *not* be used strictly
      to dial out to other hosts.  It has to be a full host
      in that it must be accessible from a remote user, and
      probably from remote hosts and other workstations as
      well.  (gee, sounds like I just read RFC 782)

-Rich
-------