Learning DCOM

Dumb Terminals

Figure 1-1 shows a dumb terminal that displays output from a remote, monolithic process running on a gigantic mainframe or a powerful UNIX server. Note that the dumb terminal does no work, except to serve as remote eyeglasses into the process running on the mainframe through some type of direct link.

Figure 1-1. Dumb terminals and large machines

In the 1950s and 1960s, large enterprises normally leased a mainframe so many employees could share it to perform routine tasks. Since there were so few of these machines (and because they were so expensive), engineers came up with ways to use mainframes remotely. One of these ideas included a dumb terminal. The communication technique behind a dumb terminal was extremely simple. The engineers literally took a wire and connected it from a dumb terminal to the host mainframe. In this respect, a dumb terminal didn’t have to determine where to send the data, because it communicated with the mainframe through a direct link.

People used dumb terminals to access the mainframe from a distance. In a sense, the mainframe moved a bit closer to the users, and since moving closer brought comfort, the users asked for more. Thus, dumb terminals quickly led to the birth of smarter terminals. These more intelligent terminals often contained specialized circuitry, firmware, and possibly a communications protocol to specifically collaborate with ...