<P>Two samples that demonstrate usage of <B>global.asa</B>. In this file you can write code that will
be executed when the application starts or session is created. Also some objects used widely in the ASP
pages of your application can be created in this file.
</P>
<p>The first sample just shows an Application and a Session variable set in the global.asa file. The second 
sample is a remake of the fetch sample for the NetProbe object but implemented in different manner. The 
NetProbe object is created in the global.asa and is available for the entire application. So the sample ASP
page uses the object that already exists and using its pooling methods ensures the other pages will wait if
they need the same object to send some requests.
</p>
<P>In ALP there is not considerable difference between ASP Application and Session except that the Session
lifetime is small. By default it is 20 minutes (can be changed in the application configuration). However 
when IIS compatibility is a requirement some advanced tehcniques will benefit of careful planning of the 
Application and Session objects and their collections.
</P>
<P>Global.asa is convenient place for code which should be executed once per session/application life. And this is
true for both ALP and IIS. However ALP/IIS compatibility may need more care. ALP will permit actions that IIS
will not. For example IIS will not permit you to keep non-freethreaded object in the Application if you try to
do so in ASP page (ALP will permit this). In global.asa this can be done in manner compatible with the both
environments - using the OBJECT tag. We recommed you to read the information about the IIS specifics in MSDN 
if the cross-compatibility is important for yor application. ALP runs for one user and is able to do things not
possible in server environment like IIS.
</P>
<p>Another ALP specific is that ALP does not support Session_OnEnd and Application_OnEnd events. The code that exist
in global.asa ported from IIS will cause no harm but will not be executed. This may cause minor problems in some rare 
cases. All the objects and other resources reserved in the Session and Application will be released when they end but
the mentioned events will not be fired. 
</P>