Path: utzoo!attcan!uunet!husc6!bloom-beacon!bu-cs!purdue!i.cc.purdue.edu!j.cc.purdue.edu!pur-ee!a.cs.uiuc.edu!uxc.cso.uiuc.edu!uxe.cso.uiuc.edu!krauskpf From: krauskpf@uxe.cso.uiuc.edu Newsgroups: comp.protocols.appletalk Subject: Re: Troubles with NCSA Telnet 2.1 Message-ID: <66000024@uxe.cso.uiuc.edu> Date: 16 Jul 88 19:36:00 GMT References: <4085@saturn.ucsc.edu> Lines: 22 Nf-ID: #R:saturn.ucsc.edu:4085:uxe.cso.uiuc.edu:66000024:000:826 Nf-From: uxe.cso.uiuc.edu!krauskpf Jul 16 14:36:00 1988 The TCP/IP protocol allows for the current window size of unacknowledged data to be sent before any sort of pause will occur. NCSA Telnet can be configured with window sizes of 512 to 4096 bytes, so this can be quite a problem. Some implementations use TCP's urgent data to signal stream controls in front of user data, but nothing I would call a standard. Instead of that, we have tried to put some helpful commands in the user interface. In version 2.1 you will find that Command-S (Suspend Network) is a local "scroll-lock" feature that will replace Ctrl-S, only it works locally. In version 2.2 you will find not only Suspend Network, but Jump Scroll which allows you to skip over those 4-10 pages of text without waiting for it to scroll by. Tim Krauskopf NCSA timk@ncsa.uiuc.edu