Charles Hedrick (firstname.lastname@example.org)
Sun, 16 Nov 86 18:26:11 est
We use Bridge CS100's extensively. We normally set them to be transparent.
I.e. ^O ^S ^Q get passed to the host. We set ^\ to do both XON and XOFF
locally. (This character doesn't seem to be needed by any of our software.
You can choose another if you prefer.) ^S takes too long to work through
the network to be useful, so we felt we had to supply some local ability
to pause output. But the ^S character would be a disaster, since it is
uased by Emacs for search. The problem of terminating output (^O and ^C)
can be solved within the telnet protocol. Bridge supports the Telnet
synch. When the host clears its output buffer, it sends an out of
band notification to the server, with an inband mark to say where
discarding data should stop. We implemented the host end on our
Pyramids. ^O still ddoesn't work instantly, but it is good enough for
At some point terminal service will put a load on your Ethernet. But
that point is several thousand users.
If your system is going to be used for heavy timesharing, the host end
of telnet will use some CPU time. For a couple of users I wouldn't
expect to see an effect. Also, character echo will slow down as the
system gets loaded, since telnetd has to be shceduled twice for each
character. On our Pyramids we put telentd in the kernel, which both
removes the loading effect and removes the echo delay. We have not
tried this on the Sun, but no doubt we will eventually.
The terminal server is a lot more flexible. We are tending to use
that for most new terminals. But it is more complex, and so there
are more things that can go wrong. Where we have a machine whose
users will always be connected to that one machine, we still use
direct terminals. But that is increasingly rare.
This archive was generated by hypermail 2.0b3 on Thu Mar 09 2000 - 14:36:59 GMT