Browse Prior Art Database

Transaction Enabled File Transfer Protocol (FTP) with eXtensible Markup Language (XML) Manifest Disclosure Number: IPCOM000028076D
Original Publication Date: 2004-Apr-22
Included in the Prior Art Database: 2004-Apr-22
Document File: 3 page(s) / 93K

Publishing Venue



FTP with XML Manifest provides a mechanism whereby the receiver of the FTP files can independently determine: 1) A group of files representing a single transaction, 2) the status of the transfer ... i.e. have all files been fully received.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 53% of the total text.

Page 1 of 3

Transaction Enabled File Transfer Protocol (FTP) with eXtensible Markup Language (XML) Manifest

Transaction Enabled File Transfer Protocol (FTP) does not provide a standard mechanism whereby the completion of the ftp process is made known to the receiver of the file(s). Therefore, it is difficult for the receiver to determine when subsequent processing of the received files may begin. Although methods exist for the sender to indicate to the receiver that the ftp process has completed (presence of a file, change name of the file after the put, etc), each of these methods is reliant upon the sender to take an action not directly related to the transfer of the file itself. The receiver has no mechanism of control.

The eXtensible Markup Language (XML) Manifest file is the key to Transaction Enabled FTP with XML Manifest. The main difficulty with FTP (from the receiver's point of view) is determining when the FTP process has completed for any given file. The XML Manifest solves this problem by including a list of files that must be received to begin processing the transaction, and also including an MD5 hash such that it can be determined if the file has been fully received. Now the receiver, by scanning for new Manifest files, can determine if the Manifest has been fully received (if it has not, the XML validating parser will reject the file), and also if each file listed in the Manifest has been fully received (if not, the calculated MD5Hash will not match the docume...