?? 00000016.htm
字號:
The foregoing, of course, does not apply to the user-to-server <br /> direction of communication. In this direction, GAs may be sent at <br /> any time, but need not ever be sent. Also, if the TELNET <br /> connection is being used for process-to-process communication, GAs <br /> need not be sent in either direction. Finally, for <br /> terminal-to-terminal communication, GAs may be required in <br /> neither, one, or both directions. If a host plans to support <br /> terminal-to-terminal communication it is suggested that the host <br /> provide the user with a means of manually signaling that it is <br /> time for a GA to be sent over the TELNET connection; this, <br /> however, is not a requirement on the implementer of a TELNET <br /> process. <br /> Note that the symmetry of the TELNET model requires that there is <br /> an NVT at each end of the TELNET connection, at least <br /> conceptually. <br /> STANDARD REPRESENTATION OF CONTROL FUNCTIONS <br /> As stated in the Introduction to this document, the primary goal <br /> of the TELNET protocol is the provision of a standard interfacing <br /> of terminal devices and terminal-oriented processes through the <br /> network. Early experiences with this type of interconnection have <br /> shown that certain functions are implemented by most servers, but <br /> that the methods of invoking these functions differ widely. For a <br /> human user who interacts with several server systems, these <br /> differences are highly frustrating. TELNET, therefore, defines a <br /> standard representation for five of these functions, as described <br />Postel & Reynolds [Page 6] <br /> <br />RFC 854 May 1983 <br /> below. These standard representations have standard, but not <br /> required, meanings (with the exception that the Interrupt Process <br /> (IP) function may be required by other protocols which use <br /> TELNET); that is, a system which does not provide the function to <br /> local users need not provide it to network users and may treat the <br /> standard representation for the function as a No-operation. On <br /> the other hand, a system which does provide the function to a <br /> local user is obliged to provide the same function to a network <br /> user who transmits the standard representation for the function. <br /> Interrupt Process (IP) <br /> Many systems provide a function which suspends, interrupts, <br /> aborts, or terminates the operation of a user process. This <br /> function is frequently used when a user believes his process is <br /> in an unending loop, or when an unwanted process has been <br /> inadvertently activated. IP is the standard representation for <br /> invoking this function. It should be noted by implementers <br /> that IP may be required by other protocols which use TELNET, <br /> and therefore should be implemented if these other protocols <br /> are to be supported. <br /> Abort Output (AO) <br /> Many systems provide a function which allows a process, which <br /> is generating output, to run to completion (or to reach the <br /> same stopping point it would reach if running to completion) <br /> but without sending the output to the user's terminal. <br /> Further, this function typically clears any output already <br /> produced but not yet actually printed (or displayed) on the <br /> user's terminal. AO is the standard representation for <br /> invoking this function. For example, some subsystem might <br /> normally accept a user's command, send a long text string to <br /> the user's terminal in response, and finally signal readiness <br /> to accept the next command by sending a "prompt" character <br /> (preceded by <CR><LF>) to the user's terminal. If the AO were <br /> received during the transmission of the text string, a <br /> reasonable implementation would be to suppress the remainder of <br /> the text string, but transmit the prompt character and the <br /> preceding <CR><LF>. (This is possibly in distinction to the <br /> action which might be taken if an IP were received; the IP <br /> might cause suppression of the text string and an exit from the <br /> subsystem.) <br /> It should be noted, by server systems which provide this <br /> function, that there may be buffers external to the system (in <br />Postel & Reynolds [Page 7] <br /> <br />RFC 854 May 1983 <br /> the network and the user's local host) which should be cleared; <br /> the appropriate way to do this is to transmit the "Synch" <br /> signal (described below) to the user system. <br /> Are You There (AYT) <br /> Many systems provide a function which provides the user with <br /> some visible (e.g., printable) evidence that the system is <br /> still up and running. This function may be invoked by the user <br /> when the system is unexpectedly "silent" for a long time, <br /> because of the unanticipated (by the user) length of a <br /> computation, an unusually heavy system load, etc. AYT is the <br /> standard representation for invoking this function. <br /> Erase Character (EC) <br />
?? 快捷鍵說明
復制代碼
Ctrl + C
搜索代碼
Ctrl + F
全屏模式
F11
切換主題
Ctrl + Shift + D
顯示快捷鍵
?
增大字號
Ctrl + =
減小字號
Ctrl + -