I beg to differ. HTTP is far better for any usecase than FTP. I understand that sometimes one has to work because of constraint imposed from parties beyond the

I beg to differ. HTTP is far better for any usecase than FTP. I understand that sometimes one has to work because of constraint imposed from parties beyond the control of the project. This may force one to support FTP. But FTP is still a terrible protocol. Uploading files to a directory and processing those from a batch job is not a proper solution to an event driven solution. > To us, it is the only highly available and reliable one. As one who has had some experience with FTP I must say that you should consider reading after the meaning of HA and reliability. > Web services have downtimes and re-sends This is pure bullshit, pardon my French. How does FTP save you from a connection trouble? How does FTP have less downtime? FTP is a stateful protocol, cannot be simply load balanced and made HA. Also idempotency makes some HTTP operations safe to redo if connection troubles arouse. For really huge amounts of data there is BitTorrent.