#use wml::openssl-macros area=docs page=OPENSSL_Applink

<title>Documents, OPENSSL_Applink(3)</title>

<h1>OPENSSL_Applink(3)</h1>

#use wml::imp::generic

{:
## What's this? [[s|(<STRONG>[^<].+?)</A>(</STRONG><DD>)|$1$2|sg]]
[[s|<P>\s+<P>|<P>|sg]]
[[s|<P>\s+</|</|sg]]
[[s|<DD>\s*<DT>|<DD>&nbsp;<DT>|sg]]
[[s|<DD>\s*</DL>|<DD>&nbsp;</DL>|sg]]
[[s|\[|&#91;|sg]]
[[s|\]|&#93;|sg]]

<!-- INDEX BEGIN -->

<UL>

	<LI><A HREF="#NAME">NAME</A>
	<LI><A HREF="#SYNOPSIS">SYNOPSIS</A>
	<LI><A HREF="#DESCRIPTION">DESCRIPTION</A>
</UL>
<!-- INDEX END -->

<HR>
<P>
<HR>
<H1><A NAME="NAME">NAME</A></H1>
<P>
OPENSSL_Applink - glue between OpenSSL BIO and Win32 compiler run-time

</P>
<P>
<HR>
<H1><A NAME="SYNOPSIS">SYNOPSIS</A></H1>
<PRE> __declspec(dllexport) void **OPENSSL_Applink();
</PRE>
<P>
<HR>
<H1><A NAME="DESCRIPTION">DESCRIPTION</A></H1>
<P>
OPENSSL_Applink is application-side interface which provides a glue between
OpenSSL BIO layer and Win32 compiler run-time environment. Even though it
appears at application side, it's essentially OpenSSL private interface.
For this reason application developers are not expected to implement it,
but to compile provided module with compiler of their choice and link it
into the target application. The referred module is available as
&lt;openssl&gt;/ms/applink.c.

</P>
:}