Considering that the bandwith used is constant, why is FTP used extensively for transfferring files of large size compared to HTTP? Even though HTTP can accomplish the same task.
I undersand that FTP is a diiferent protocol and HTTP is different protocol and they both use different ports. But what is the distinguishing factor here?
Considering that the bandwith is constant for HTTP %26amp; FTP, why is FTP extensively used?
FTP does tend to be easier to script access to. Not sure about performance benchmarks though. Through shell scripting, I can easily script get/put to an FTP site where an HTTP location would require a more traditional application.
Considering that the bandwith is constant for HTTP %26amp; FTP, why is FTP extensively used?
FTP is older and more established, and better at resuming a partial download. It also uses less "extra" padding bandwidth than http.
For given hardware and bandwidth, an FTP server can serve more customers/clients/files than the same hardware and bandwidth using http.
Reply:ftp was designed to transfer files and have minimal control over upload/download location and permissions of the files. Http was designed as a markup language to display text and images (it just happened to evolve past there). FTP is still in use because old habits are hard to break for one, and second, it's a fairly elegant solution for file transfers. It is going away little by little, but won't be gone completely for quite some time.
Reply:For us old-school folk, FTP was also used before Windows and the Internet were popular. IT was used at the DOS and UNIX command line levels.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment