| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
FTP Operational Model, Protocol Components and Key Terminology (Page 1 of 4) The standards that define the File Transfer Protocol (FTP) describe its overall operation using a simple conceptual tool called the FTP model. This model defines the roles of the devices that participate in a file transfer, and the two communication channels that are established between them. It also describes the components of FTP that manage these channels, and defines the terminology used for the components. This makes it an ideal place for us to see how FTP works in broad terms. FTP is a classical client/server protocol, as I mentioned in the overview. However, the client is not called by that name but rather is called the user. The name comes from the fact that the human user that issues FTP commands works on the client machine. The full set of FTP software operating on a device is called a process. The FTP software on the server is called the Server-FTP Process, while the software on the client is the User-FTP Process.
A critical concept in understanding FTP is that while it uses TCP like many other applications, it does not use just one TCP connection for all communication the way most protocols do. The FTP model is designed around two logical channels of communication between the server and user FTP processes:
The reason for having these separate channels is that it provides flexibility in how the protocol is used, as we will see later in this section. It does, however, add complexity to FTP.
Home - Table Of Contents - Contact Us The TCP/IP Guide (http://www.TCPIPGuide.com) Version 3.0 - Version Date: September 20, 2005 © Copyright 2001-2005 Charles M. Kozierok. All Rights Reserved. Not responsible for any loss resulting from the use of this site. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||