<P>
    <B>Dump the request</B>. This sample shows a listing of the request contents - query string variables, form
    post and server variables. Although the sample is not ALP specific it is in this area to show the 
    environment differences between IIS and ALP.
</p>
<p>
    There is noting special about the Request.QueryString and Request.Form collections in ALP, except that
    they are more featured collections than the corresponding collections in IIS and in ALP you can
    perform more operations with them. But ServerVariables contents is different. You can see for your self
    how ALP makes the ASP pages comfortable by serving information in the appropriate variables,
    but information that is a bit different than in IIS.
</P>
<p>
    for example in IIS SERVER_NAME may look like this:<BR>
    <B>www.server.com</B><BR>
    In ALP you will see something like:<BR>
    <B>C:/directory/directory/</B><BR>
    Thus ALP &quot;says the truth&quot; in the variables but in a way that will prevent the applications from
    confusion. The only case that can be a problem is if the ASP page wants to perform DNS lookup over the name
    - the lookup will fail. In all other cases the fact that ALP substitutes the host names with local paths is
    rather helpful than cumbersome feature.
</P>
<p>
    There is a certain relation between the context of these variables and the ALP configuration files - alp.site and
    alp.application. As in IIS in ALP you have ability to create virtual sites and isolated ASP applicaitons. While
    IIS determines them by reading its configuration metabase - ALP does this by inspecting the file system tree 
    containing the application. The mere existence of alp.site file in certain directory denotes it and its subtree
    as <I>virtual server</I> or also called in our documentation <I>ALP site</I>. ALP treats the full path name of this
    directory as like host name and serves it in the server variables. The similar is the case with alp.application and
    APPL_PHYSICAL_PATH variable - but this is the path of the ASP application.
</p>
<p>
    ALP does not support virtual directories and will not support them. The reason is obvious - keep the ALP applications
    intact when moved. You can copy entire ALP application directory tree and run it from other location - with virtual 
    directories the application files will spread and it will be hard to move them - even impossible sometimes. So
    the price for the easy deployment are the virtual directories.
</p>