RFC 398 UNKNOWN GRAPHICS · SERVICES

UCSB Online Graphics

Directory of socket addresses for UCSB online graphics services

On rfc-editor.org ↗
PUBLISHED
September 1972
AUTHORS
J.R. Pickens, E. Faeh
STREAM
Legacy
IMLAC SOCKET (POWELL SOFTWARE)
x'701'
IMLAC SOCKET (80X80 GRID)
x'703'
LEVEL 0 PROTOCOL SOCKET
x'705'
TEKTRONIX SOCKET
x'801'
DOI
10.17487/RFC0398

RFC text

Original text · RFC Editor View on rfc-editor.org ↗
NWG/RFC #398                                        John R. Pickens
UCSB Online Graphics                                Edward D. Faeh
NIC 11911                                           UCSB
                                                    22 Sept 72

At present, users with TEKTRONIX or IMLAC terminals or with systems
that support the proposed level 0 graphics protocol can access UCSB
graphics.  Listed below are the ICP sockets for the currently
supported terminals and protocols.  Any detailed questions about or
problems with a particular protocol should be directed to Ed Faeh
(805-961-4047).

   Socket                       Supports

   x'701'               IMLAC with special software designed
                        by Jerry Powell (MITRE Corp.).
                        Graphics is sent over a simplex
                        connection to the IMLAC.  Alphanumerics
                        are sent over a TELNET-like connection
                        to a separate device.  The IMLAC
                        software can be loaded from MIT-DMCG.

   x'703'               IMLAC with 80x80 display grid
                        and Standard Text and Edit Package.
                        Some IMLACs have a 64x64 display grid.
                        Therefore, the choice may be made in
                        the near future to format the
                        graphics output from this connection
                        for the smaller grid resolution so
                        that both terminal types may be handled.
                        Display resolution is limited with
                        this terminal configuration as
                        normal UCSB terminals have 1024x1024
                        grid.  Nevertheless, meaningful
                        displays are obtained even at the
                        lower resolutions.

   x'705'               Current Level 0 graphics protocol.

   x'707'               Same as x'701' but with special
                        UCSB online keyboard as input.
                        This configuration averts the
                        necessity of spelling out online
                        operators.

   x'709'               Same as x'705' but with special
                        UCSB online keyboard as input.

NWG/RFC# 398                        JRP EDF 22-SEP-72 16:25  11911
UCSB OnLine Graphics


   x'801'               TEKTRONIX terminals.  Models 4002-A
                        4010, and T-4002 have been tested
                        successfully.  Presumably all other
                        4002 compatible terminals will also work.

The primary problems that will be encountered by the network user
center about display formatting.  For historical reasons (i.e.  only
one type of terminal in house ) no means were included in the system
to facilitate terminal independent random positioning of alphanumeric
output.  Thus, a program which draws and labels a graph neatly on one
terminal might label like a kindergartener on other terminals.
Nevertheless, this problem can be minimized with careful programming
and efforts are underway to provide at least minimal alphanumeric
device independence.

Users interested in experimenting with online graphics should contact
John Pickens (805-961-3454), Glen Davis (805-961-2462), or Mark
Krilonovich (805-961-3454).  Suggestions and criticisms of all aspects
of the UCSB OnLine - Network User interface are desired.






       [ This RFC was put into machine readable form for entry ]
       [ into the online RFC archives by BBN Corp. under the   ]
       [ direction of Alex McKenzie.                      1/97 ]

AI ELI5

On this page
PROBLEMUCSB had several graphics protocols available on the network, but users needed to know which socket (ICP address) to connect to for each type of terminal.
MECHANISMThis RFC lists five socket addresses that support different graphics terminals and protocols: IMLAC with standard software, IMLAC with 80x80 display grid, Level 0 graphics protocol, and TEKTRONIX terminals.
SERVICE DIRECTORYThe socket list made it easy for remote users to access UCSB's graphics capabilities using whatever terminal hardware they had.

§1UCSB Graphics on the Network

UCSB provided online graphics services to ARPANET users. Users with TEKTRONIX or IMLAC display terminals, or systems supporting the Level 0 graphics protocol, could access UCSB graphics. The RFC lists the ICP (Initial Connection Port) socket addresses for each supported terminal type, with contact information for detailed questions.

UCSB has drawing machines you can use from your terminal over the network. This tells you which address to connect to for your type of machine.

§2Supported Terminal Types

The RFC documents five socket configurations. IMLAC terminals with special software designed by Jerry Powell send graphics over a simplex connection and alphanumerics over a TELNET-like connection. Another socket serves IMLAC terminals with an 80x80 display grid and standard text editing (though some IMLACs had 64x64 grids). TEKTRONIX terminals including models 4002-A, 4010, and T-4002 were tested successfully, and the system expected all other 4002-compatible terminals to work.

Different drawing screens need different connections. Some have fancy keyboards built in, some share a text connection, and some are tested with TEKTRONIX machines.

§3Formatting Challenges

A primary problem encountered by users centered on display formatting. The system lacked terminal-independent positioning for alphanumeric output because only one terminal type had been in house during design. Programs that drew and labeled graphs neatly on one terminal might not display properly on others. Efforts were underway to provide at least minimal device independence, and users were encouraged to contact John Pickens, Glen Davis, or Mark Krilonovich with suggestions and criticisms.

Text labels sometimes appear in the wrong spot on different screens because the system was built for only one type. The team is working on making it better.