User's Manual

♦ Some message systems, including SMTP, VIM, and MAPI, require
text-based message formats. For these systems, an encoding DLL
( dbencod.dll for Adaptive Server Anywhere and ssencod.dll for Adaptive
Server Enterprise) translates messages into a text format before sending.
The message format is unencoded at the receiving end using the same
DLL.
♦ You can instruct SQL Remote to use a custom encoding scheme. The
tools for building a custom encoding scheme are described in the
following section.
♦ If the COMPRESSION database option is set to -1, then a Version 5
compatible encoding is carried out for all message systems.
Creating custom encoding schemes
You can implement a custom encoding scheme by building a custom
encoding DLL. You could use this DLL to apply special features required
for a particular messages system, or to collect statistics, such as how many
messages or how many bytes were sent to each user.
The header file dbrmt.h , installed into the h subdirectory of your installation
directory, provides an application programming interface for building such a
scheme.
To instruct SQL Remote to use your DLL for a particular message system,
you must make a registry entry for that system. The registry entry should be
made in the following location:
Software
\Sybase
\SQL Remote
\message-system
\encode_dll
where message-system is one of the SQL Remote message systems (file,
smtp, and so on). You should set this registry entry to the name of your
encoding DLL.
Encoding and decoding must be compatible
If you implement a custom encoding, you must make sure that the DLL is
present at the receiving end, and that the DLL is in place to decode your
messages properly.
236