What are the main differences between FSP and FTP? How does FSP work?
From the user’s point of view, the differences are not that great, except that some of the more annoying features of FTP are gone. Here are the main differences. • The protocol can stand things going down: if the server or the network falls over in the middle of a transfer, you can just wait until it comes back up. You don’t have to reconnect, and even better, if the server went down 90% through grabbing a file, you can continue from where you left off. • The protocol doesn’t need a username or password. You just throw packets at the server. You don’t have to identify yourself (though you’re not completely anonymous — see below). • It’s harder to kill off a site with an FSP server than with an FTP server. The FSP daemon is designed to be as lightweight as possible: it doesn’t fork off any sub-processes, and it takes steps to limit the amount of traffic it handles. • The user interface is completely different. The interface that comes with the package consists of eleven commands that y