For some entities in the health care industry, file transfer activities are no longer as simple as before. Measures have to be taken to make sure violations aren't made against HIPAA. FTP services, perhaps the most widely used services for transferring large files over the Internet, now require enhancements to ensure that data considered as electronic protected health information (ePHI) are protected throughout an FTP transfer.
Managed File Transfer and Network Solutions
When two little kids want to exchange a secret, a lot of negotiation is necessary: "Promise you won't tell? Cross your heart and hope to die?". When a client and server computer want to exchange secrets, they need to negotiate too: public keys, encryption methods, ports and more. Fortunately, JSCAPE's Secure FTP Factory and server software (such as JSCAPE MFT Server) handle most of the details for you.
Here's some philosophy to go with the Secure FTP Factory library. There are some things in life that you should never do unless you feel completely secure. One of them is withdrawing money from an ATM. You should do this only in a safe, well lit and preferably high traffic environment where you are unlikely to be robbed. Another is uploading or downloading files using plain FTP (File Transfer Protocol).
Streamlined FTP Command Extensions is a proposal for 5 new FTP commands. I stress the word proposal, because it seems to have been abandoned, and would not progress to Internet Standard without a good deal of effort. That said, there was a decent amount of interest in at least some of the commands. I'm going to quote liberally from it for some of the descriptions.
Standard FTP already has the REST command, which allows the starting point of a file transfer to be specified:
FTP is quite a stable protocol. It's been used for nearly 4 decades to transfer files. FTP is defined in a series of RFCs (Internet Standards or specifications that describe how to implement the protocol) which are published by the Internet Engineering Task Force (IETF), a standards developing organization.
Many different specifications (RFCs) over the long history of FTP describe its official implementation. FTP is about 40 years old, but there are about 10 "newer" specifications written over the last 25 years that implementors need to take into account, only some of which are linked to each other. You might not find them, even if you know what you're looking for! :)
FTP originated at a time before virtual hosting, where multiple servers are hosted on a single IP address but with different domain names. On the Internet, multiple domain names may resolve to a single IP address.