...
The configurations described in this tutorial can be downloaded and then directly opened in the XML Editor using the following links:
...
. Links for each configuration are available at the start of each section of this tutorial.
Checking files for completeness
...
- Integrity hash checksums such as MD5, which are generated before file transfer starts and can be used to check files carry out a before / after comparison of file size after transfer has been completed.
- Atomic file transfer, which is used to hide files being transferred from target directory monitors until the file transfer has been completed.
- A prefix and/or suffix is added to the name of the file for the duration of the transfer.
This prefix/suffix is chosen so that the file being transferred will not be matched by any target host file monitor. - Once transfer has been completed, JADE removes the prefix/suffix and the file becomes visible to a file monitor.
- A prefix and/or suffix is added to the name of the file for the duration of the transfer.
- Regularly checking the file size until it reaches a steady state. Here it is assumed that the transfer has been completed when two checks in series return the same size.
...
- This example uses a set of 5 test_*.txt files that have been saved into to the user's \jade_demo\a directory by local file system during the implementation of an earlier tutorial in this series - for example The JADE Client Command Line Interface - Tutorial 1 - Getting Started in which the files were downloaded to the user's
\jade_demo\adirectory. - A ProtocolFragment is not required in the configuration of this example, as local to local transfer is being carried out.
...
If you have already run some of the examples described in previous examplestutorials, you will have a series of files in the ${USERPROFILE}\jade_demo\a directory on your computer, sequentially named test_1.txt through to test_5.txt.
...