<P>ALP DLL Objects are in-process COM objects (compiled in DLL) with automation 
interface support (IDispatch). The sample illustrates how to write and use such 
a component in VB. The sample component is quite simple - it just lists the ALP
server variables.</P>

<P>ALP supports components created especially for it the same way the IIS does it
but with certain limitations caused by the following ALP aims:
</P>
<UL>
	<LI>ALP must not depend on MTX (COM+ services) because it is supposed to 
		work on platforms without it.
	</LI>
	<LI>ALP differs from IIS and is not binary compatible with it. Therefore the
	COM objects created for ALP should use automation based communication with ALP and
	not binary interfaces (see below).
	</LI>
</UL>
<P>
	The ALP objects are COM objects implementing IDispatch (automation interface) and
	two special methods - <B>OnStartPage(ctx)</B> and <B>OnEndPage</B>. The ctx variable passed 
	to the first one is ALP contextobject that contains the ASP objects for the current request.
	The object can save them in local variables (only the objects it is going to use of course)
	and then perform its work by directly accessing the ALP context data.
</P>
<P>
	The context passed should be treated as scriptable object and called through IDispatch
	even if you are writting an ALP object in C++! This will ensure its compatibility with IIS and
	other ASP implementations.
</P>