Larry Leeth
New Member
I understand the use of encode for password management.
What I an interested in is how well 'encode' compares to general one-way hash algoriths such as SHA-1, especially on large files.
The application would be to generate an output file (archived DB records), compute a 'hash' on the file, and store the file name & hash value. When there is a need to reload the archive data, the file could be validated by re-computing the 'hash' and comparing it to the stored value. If the hash values match, the archive reload would be allowed to proceed.
Sound familiar to password varification?
Since 'encode' is more generally applied to very short strings, is it a candidate for this type of application? Are there other 'performant' Progress solutions?
Larry
What I an interested in is how well 'encode' compares to general one-way hash algoriths such as SHA-1, especially on large files.
The application would be to generate an output file (archived DB records), compute a 'hash' on the file, and store the file name & hash value. When there is a need to reload the archive data, the file could be validated by re-computing the 'hash' and comparing it to the stored value. If the hash values match, the archive reload would be allowed to proceed.
Sound familiar to password varification?
Since 'encode' is more generally applied to very short strings, is it a candidate for this type of application? Are there other 'performant' Progress solutions?
Larry