Comparison of file transfer protocols

src: www.mcs.anl.gov

This article lists communication protocols that are designed for file transfer over a telecommunications network.

Protocols for shared file systems--such as 9P and the Network File System--are beyond the scope of this article, as are file synchronization protocols.

Video Comparison of file transfer protocols

Protocols for packet-switched networks

A packet-switched network transmits data that is divided into units called packets. A packet comprises a header (which describes the packet) and a payload (the data). The Internet is a packet-switched network, and most of the protocols in this list are designed for its protocol stack, the IP protocol suite.

They use one of two transport layer protocols: the Transmission Control Protocol (TCP) or the User Datagram Protocol (UDP). In the tables below, the "Transport" column indicates which protocol(s) the transfer protocol uses at the transport layer. Some protocols designed to transmit data over UDP also use a TCP port for oversight.

The "Server port" column indicates the port from which the server transmits data. In the case of FTP, this port differs from the listening port. Some protocols--including FTP, FTP Secure, FASP, and Tsunami--listen on a "control port" or "command port", at which they receive commands from the client.

Similarly, the encryption scheme indicated in the "Encryption" column applies to transmitted data only, and not to the authentication system.

Overview

Features

Managed file transfer

Protocols for managed file transfer prioritise secure transmission in industrial applications that require such features as auditable transaction records, monitoring, and end-to-end data security. Such protocols may be preferred for electronic data interchange.

Maps Comparison of file transfer protocols

Serial protocols

The following protocols were designed for serial communication, mostly for the RS-232 standard. They are used for uploading and downloading computer files via modem or serial cable (e.g., by null modem or direct cable connection). UUCP is one protocol that can operate with either RS-232 or the Transmission Control Protocol as its transport. OBject EXchange is a protocol for binary object wireless transfer via the Bluetooth standard. Bluetooth was conceived as a wireless replacement for RS-232.

Overview

Features

src: www.smartfile.com

See also

src: cdn.comparitech.com

Notes

src: edgeoptic.com

References

• da Cruz, Frank (1987). Kermit: A File Transfer Protocol. Bedford: Digital Press. ISBN 0-932376-88-6. OCLC 751527576 - via Google Books. 
• Glass, Brett (30 May 1988). "Xmodem Popular for Its Simplicity, Public Domain Status". InfoWorld - via Google Books. 
• Lottor, Mark K. (September 1984). Simple File Transfer Protocol. IETF. doi:10.17487/RFC0913. RFC 913. https://tools.ietf.org/html/rfc913. Retrieved 2018-03-01. 

src: slideplayer.com

Further reading

• de Goyeneche, Juan-Mariano (20 March 1998). "Multicast Transport Protocols". Multicast over TCP/IP HOWTO - via The Linux Documentation Project. 
• Kaplan, Ali (2009). "Literature Survey". Collaborative Framework for High-Performance P2P-based Data Transfer in Scientific Computing (DOCX) (Ph.D. thesis). Indiana University Bloomington. pp. 12-39. ISBN 978-1-109-50327-2. OCLC 648765323. 
• Kientzle, Tim (1995). The Working Programmer's Guide to Serial Protocols. Coriolis Group Books. ISBN 1-883577-20-9. OCLC 441637109. 
• "Kermit FAQ". KermitProject.org. The Kermit Project. 

Source of article : Wikipedia