Apache-ASP

 view release on metacpan or  search on metacpan

ASP.pm  view on Meta::CPAN


  http://search.cpan.org/dist/Apache-ASP/
  http://cpan.org/modules/by-module/Apache/

As a Perl developer, you should make yourself familiar with 
the CPAN.pm module, and how it may be used to install
Apache::ASP, and other related modules.  The easiest way
to install Apache::ASP for the first time from Perl is to 
fire up the CPAN shell like:

 shell prompt> perl -MCPAN -e shell
  ... configure CPAN ...
  ... then upgrade to latest CPAN ...
 cpan> install CPAN
  ...
 cpan> install Bundle::Apache::ASP

Installing the Apache::ASP bundle will automatically install
all the modules Apache::ASP is dependent on as well as
Apache::ASP itself.  If you have trouble installing the bundle,
then try installing the necessary modules one at a time:

ASP.pm  view on Meta::CPAN

the perl Win32::OLE interface.  This will remain true until there
are free COM ports to the UNIX world.  At this time, there is no ActiveX
for the UNIX world.

=head2 Support and Production

=item How do I get things I want done?!

If you find a problem with the module, or would like a feature added,
please mail support, as listed in the SUPPORT section, and your 
needs will be promptly and seriously considered, then implemented.

=item What is the state of Apache::ASP?  Can I publish a web site on it?

Apache::ASP has been production ready since v.02.  Work being done
on the module is on a per need basis, with the goal being to eventually
have the ASP API completed, with full portability to ActiveState PerlScript
and MKS PScript.  If you can suggest any changes to facilitate these
goals, your comments are welcome.

=head1 TUNING

ASP.pm  view on Meta::CPAN

  config setting.

 +Better pre-fork caching ... StatINC & StatINCMatch are now 
  args for Apache::ASP->Loader(), so StatINC symbols loading
  may be done pre-fork and shared between httpds.  This lowers
  the child httpd init cost of StatINC.  Documented.

 +Made Apache::ASP Basic Authorization friendly so authentication
  can be handled by ASP scripts.  If AuthName and AuthType Apache
  config directives are set, and a $Response->{Status} is set to 
  401, a user will be prompted for username/password authentication
  and the entered data will show up in ServerVariables as:
    $env = $Request->ServerVariables
    $env->{REMOTE_USER} = $env->{AUTH_USER} = username
    $env->{AUTH_PASSWD} = password
    $env->{AUTH_NAME}   = your realm
    $env->{AUTH_TYPE}   = 'Basic'

  This is the same place to find auth data as if Apache had some 
  authentication handler deal with the auth phase separately.

ASP.pm  view on Meta::CPAN

  API extensions.

 +Added AllowApplicationState config option which allows
  you to leave $Application undefined, and will not
  execute Application_OnStart or Application_OnEnd.
  This can be a slight performance increase of 2-3% if
  you are not using $Application, but are using $Session.

 +Added $Session->Lock() / $Session->UnLock() API routines
  necessary additions since access to session is not
  serialized by default like IIS ASP.  Also prompted
  by change in locking code which retied to SDBM_File
  or DB_File each lock.  If you $Session->Lock / UnLock
  around many read/writes, you will increase performance.

 +Added StateCache config which, if set will cache
  the file handle locks for $Application and an internal 
  database used for tracking $Session info.  This caching can 
  make an ASP application perform up to 10% faster,
  at a cost of each web server process holding 2 more 
  cached file handles open, per ASP application using

README  view on Meta::CPAN

    You may download the latest Apache::ASP from your nearest CPAN, and also:

      http://search.cpan.org/dist/Apache-ASP/
      http://cpan.org/modules/by-module/Apache/

    As a Perl developer, you should make yourself familiar with the CPAN.pm
    module, and how it may be used to install Apache::ASP, and other related
    modules. The easiest way to install Apache::ASP for the first time from Perl
    is to fire up the CPAN shell like:

     shell prompt> perl -MCPAN -e shell
      ... configure CPAN ...
      ... then upgrade to latest CPAN ...
     cpan> install CPAN
      ...
     cpan> install Bundle::Apache::ASP

    Installing the Apache::ASP bundle will automatically install all the modules
    Apache::ASP is dependent on as well as Apache::ASP itself. If you have
    trouble installing the bundle, then try installing the necessary modules one
    at a time:

README  view on Meta::CPAN

    Do I have access to ActiveX objects?
        Only under Win32 will developers have access to ActiveX objects through
        the perl Win32::OLE interface. This will remain true until there are
        free COM ports to the UNIX world. At this time, there is no ActiveX for
        the UNIX world.

  Support and Production
    How do I get things I want done?!
        If you find a problem with the module, or would like a feature added,
        please mail support, as listed in the SUPPORT section, and your needs
        will be promptly and seriously considered, then implemented.

    What is the state of Apache::ASP? Can I publish a web site on it?
        Apache::ASP has been production ready since v.02. Work being done on the
        module is on a per need basis, with the goal being to eventually have
        the ASP API completed, with full portability to ActiveState PerlScript
        and MKS PScript. If you can suggest any changes to facilitate these
        goals, your comments are welcome.

TUNING
    A little tuning can go a long way, and can make the difference between a web

README  view on Meta::CPAN

          config setting.

         +Better pre-fork caching ... StatINC & StatINCMatch are now 
          args for Apache::ASP->Loader(), so StatINC symbols loading
          may be done pre-fork and shared between httpds.  This lowers
          the child httpd init cost of StatINC.  Documented.

         +Made Apache::ASP Basic Authorization friendly so authentication
          can be handled by ASP scripts.  If AuthName and AuthType Apache
          config directives are set, and a $Response->{Status} is set to 
          401, a user will be prompted for username/password authentication
          and the entered data will show up in ServerVariables as:
            $env = $Request->ServerVariables
            $env->{REMOTE_USER} = $env->{AUTH_USER} = username
            $env->{AUTH_PASSWD} = password
            $env->{AUTH_NAME}   = your realm
            $env->{AUTH_TYPE}   = 'Basic'

          This is the same place to find auth data as if Apache had some 
          authentication handler deal with the auth phase separately.

README  view on Meta::CPAN

          API extensions.

         +Added AllowApplicationState config option which allows
          you to leave $Application undefined, and will not
          execute Application_OnStart or Application_OnEnd.
          This can be a slight performance increase of 2-3% if
          you are not using $Application, but are using $Session.

         +Added $Session->Lock() / $Session->UnLock() API routines
          necessary additions since access to session is not
          serialized by default like IIS ASP.  Also prompted
          by change in locking code which retied to SDBM_File
          or DB_File each lock.  If you $Session->Lock / UnLock
          around many read/writes, you will increase performance.

         +Added StateCache config which, if set will cache
          the file handle locks for $Application and an internal 
          database used for tracking $Session info.  This caching can 
          make an ASP application perform up to 10% faster,
          at a cost of each web server process holding 2 more 
          cached file handles open, per ASP application using

site/changes.html  view on Meta::CPAN

  config setting.

 +Better pre-fork caching ... StatINC & StatINCMatch are now 
  args for Apache::ASP->Loader(), so StatINC symbols loading
  may be done pre-fork and shared between httpds.  This lowers
  the child httpd init cost of StatINC.  Documented.

 +Made Apache::ASP Basic Authorization friendly so authentication
  can be handled by ASP scripts.  If AuthName and AuthType Apache
  config directives are set, and a $Response->{Status} is set to 
  401, a user will be prompted for username/password authentication
  and the entered data will show up in ServerVariables as:
    $env = $Request->ServerVariables
    $env->{REMOTE_USER} = $env->{AUTH_USER} = username
    $env->{AUTH_PASSWD} = password
    $env->{AUTH_NAME}   = your realm
    $env->{AUTH_TYPE}   = 'Basic'

  This is the same place to find auth data as if Apache had some 
  authentication handler deal with the auth phase separately.

site/changes.html  view on Meta::CPAN

  API extensions.

 +Added AllowApplicationState config option which allows
  you to leave $Application undefined, and will not
  execute Application_OnStart or Application_OnEnd.
  This can be a slight performance increase of 2-3% if
  you are not using $Application, but are using $Session.

 +Added $Session->Lock() / $Session->UnLock() API routines
  necessary additions since access to session is not
  serialized by default like IIS ASP.  Also prompted
  by change in locking code which retied to SDBM_File
  or DB_File each lock.  If you $Session->Lock / UnLock
  around many read/writes, you will increase performance.

 +Added StateCache config which, if set will cache
  the file handle locks for $Application and an internal 
  database used for tracking $Session info.  This caching can 
  make an ASP application perform up to 10% faster,
  at a cost of each web server process holding 2 more 
  cached file handles open, per ASP application using

site/faq.html  view on Meta::CPAN

	<a name=Support%20and%20b4365dac></a>
	<font face=verdana><font class=title size=+0 color=#555555><b>Support and Production</b></font>
</font>
	
	<p>
	<a name=How%20do%20I%20get45b324ef></a>
	<font face=verdana><font class=title size=-1 color=#555555><b>How do I get things I want done?!</b></font>
<font face="courier new" size=3><pre>
</pre></font>If you find a problem with the module, or would like a feature added,
please mail support, as listed in the <a href=support.html><font size=-1 face=verdana><b>SUPPORT</b></font></a> section, and your 
needs will be promptly and seriously considered, then implemented.</font>
	
	<p>
	<a name=What%20is%20the%20bd2800a9></a>
	<font face=verdana><font class=title size=-1 color=#555555><b>What is the state of Apache::ASP?  Can I publish a web site on it?</b></font>
<font face="courier new" size=3><pre>
</pre></font>Apache::ASP has been production ready since v.02.  Work being done
on the module is on a per need basis, with the goal being to eventually
have the ASP API completed, with full portability to ActiveState <a href=http://www.activestate.com/ActivePerl/><font size=-1 face=verdana><b>PerlScript</b></font></a>
and MKS PScript.  If you can suggest any changes to facilitate these
goals, your comments are welcome.</font>

site/install.html  view on Meta::CPAN

and also:
<font face="courier new" size=3><pre>
  <a href=http://search.cpan.org/dist/Apache-ASP/>http://search.cpan.org/dist/Apache-ASP/</a>
  <a href=http://cpan.org/modules/by-module/Apache/>http://cpan.org/modules/by-module/Apache/</a>
</pre></font>As a Perl developer, you should make yourself familiar with 
the CPAN.pm module, and how it may be used to install
Apache::ASP, and other related modules.  The easiest way
to install Apache::ASP for the first time from Perl is to 
fire up the CPAN shell like:
<font face="courier new" size=3><pre>
 shell prompt&gt; perl -MCPAN -e shell
  ... configure CPAN ...
  ... then upgrade to latest CPAN ...
 cpan&gt; install CPAN
  ...
 cpan&gt; install Bundle::Apache::ASP
</pre></font>Installing the Apache::ASP bundle will automatically install
all the modules Apache::ASP is dependent on as well as
Apache::ASP itself.  If you have trouble installing the bundle,
then try installing the necessary modules one at a time:
<font face="courier new" size=3><pre>



( run in 1.431 second using v1.01-cache-2.11-cpan-6aa56a78535 )