Encode and decode files using standard algorithms such as base64,
uuencode and quoted-printable. The control can also be used to
compress and expand files, as well as encrypt or decrypt file data
using AES encryption.
||RFC 1738, RFC 1951, RFC 2045
The File Encoding control provides functions for encoding and
decoding binary files, typically attachments to email messages. The
process of encoding converts the contents of a binary file to
printable 7-bit ASCII text. Decoding reverses the process, converting
a previously encoded text file back into a binary file.
There are two primary types of encoding methods used with various
Internet applications: base64 and uucode.
The base64 algorithm is most commonly used with email attachments, and
is often referred to as MIME encoding since this is the encoding
method specified in the MIME standards document. The uucode algorithm
(so called because the programs to perform the encoding were called
uuencode and uudecode) is often used when attaching binary files to
Usenet newsgroup posts. The library also supports an alternate
encoding format called yEnc which is also widely used to attach files
to Usenet posts.
In addition to encoding and decoding data files, this control
includes methods to compress and expand data, as well as encrypt and
decrypt files using 256-bit AES encryption.
The SocketTools ActiveX Edition components are self-registering
controls compatible with any programming language that supports COM
(Component Object Model) and the ActiveX control specification. If
you are using Visual Basic 6.0 or Visual C++ 6.0, it is required that
you have Service Pack 6 (SP6) installed. It is recommended that you
install all updates for your development tools.
This component is supported on Windows XP and later versions of
the Windows desktop and server platforms. If you are using
Windows XP, you must have Service Pack 3 (SP3) installed as a minimum
requirement. It is recommended that you install the current service
pack and all critical updates available for your version of the
This product includes both 32-bit and 64-bit ActiveX controls.
Native 64-bit CPU support requires the latest 64-bit version of
Windows XP Professional, Windows Server 2003 or later versions of the
Windows operating system.
When you distribute an application that uses this control, you can
either install the file in the same folder as your application
executable or as a shared component in the appropriate system folder.
If you install the control in the system folder, it is important that
you distribute the correct version for the target platform and it
must be registered. If you install the control in the same folder as
your executable, it is recommended that you use registration-free
activation or COM redirection to ensure that the correct version of
the control is loaded by the application.