Apache-ASP

 view release on metacpan or  search on metacpan

ASP.pm  view on Meta::CPAN

XSLTParser setting, which can also use XML::Sablotron ( support added in 2.11 ), 
and XML::LibXSLT ( support added in 2.29 ). 
Please see the CONFIG section for more information on the 
XSLT* settings that drive this API.  The XSLT setting itself 
uses this API internally to do its rendering.

This API was created to allow developers easy XSLT component
rendering without having to render the entire ASP scripts
via XSLT.  This will make an easy plugin architecture for
those looking to integrate XML into their existing ASP
application frameworks.

At some point, the API will likely take files as arguments,
but not as of the 2.11 release.

=back

=head1 SSI

SSI is great!  One of the main features of server side includes 
is to include other files in the script being requested.  In Apache::ASP, 

ASP.pm  view on Meta::CPAN

	http://perl.apache.org/guide/

	Perl Programming Language
	http://www.perl.com

	Apache Web Server
	http://www.apache.org
 
=head1 TODO

There is no specific time frame in which these things will be 
implemented.  Please let me know if any of these is of particular
interest to you, and I will give it higher priority.

=head2 WILL BE DONE 

 + Database storage of $Session & $Application, so web clusters 
   may scale better than the current NFS/CIFS StateDir implementation
   allows, maybe via Apache::Session.

=head1 CHANGES

ASP.pm  view on Meta::CPAN


 -StatINC & StatINCMatch will not undef Fnctl.pm flock 
  functions constants like O_RDWR, because the code references
  are not well trackable.  This would result in sporadic 500 server
  errors when a changed module was reloaded that imported O_* flock 
  functions from Fnctl.

 +SessionQueryParse & SessionQueryParseMatch
  settings that enable auto parsing session ids into 
  URLs for cookieless sessions.  Will pick up URLs in 
  <a href>, <area href>, <form action>, <frame src>,
  <iframe src>, <img src>, <input src>, <link href>
  $Response->Redirect($URL) and the first URL in 
  script tags like <script>*.location.href=$URL</script>

  These settings require that buffering be enabled, as
  Apache::ASP will parse through the buffer to parse the URLs.

  With SessionQueryParse on, it will just parse non-absolute
  URLs, but with SessionQueryParseMatch set to some server
  url regexp, like ^http://localhost , will also parse
  in the session id for URLs that match that.

README  view on Meta::CPAN

        The XSLT parser defaults to XML::XSLT, and is configured with the
        XSLTParser setting, which can also use XML::Sablotron ( support added in
        2.11 ), and XML::LibXSLT ( support added in 2.29 ). Please see the
        CONFIG section for more information on the XSLT* settings that drive
        this API. The XSLT setting itself uses this API internally to do its
        rendering.

        This API was created to allow developers easy XSLT component rendering
        without having to render the entire ASP scripts via XSLT. This will make
        an easy plugin architecture for those looking to integrate XML into
        their existing ASP application frameworks.

        At some point, the API will likely take files as arguments, but not as
        of the 2.11 release.

SSI
    SSI is great! One of the main features of server side includes is to include
    other files in the script being requested. In Apache::ASP, this is
    implemented in a couple ways, the most crucial of which is implemented in
    the file include. Formatted as

README  view on Meta::CPAN

            mod_perl 1.x Guide
            http://perl.apache.org/guide/

            Perl Programming Language
            http://www.perl.com

            Apache Web Server
            http://www.apache.org

TODO
    There is no specific time frame in which these things will be implemented.
    Please let me know if any of these is of particular interest to you, and I
    will give it higher priority.

  WILL BE DONE
     + Database storage of $Session & $Application, so web clusters 
       may scale better than the current NFS/CIFS StateDir implementation
       allows, maybe via Apache::Session.

CHANGES
    Apache::ASP has been in development since 1998, and was production ready

README  view on Meta::CPAN


         -StatINC & StatINCMatch will not undef Fnctl.pm flock 
          functions constants like O_RDWR, because the code references
          are not well trackable.  This would result in sporadic 500 server
          errors when a changed module was reloaded that imported O_* flock 
          functions from Fnctl.

         +SessionQueryParse & SessionQueryParseMatch
          settings that enable auto parsing session ids into 
          URLs for cookieless sessions.  Will pick up URLs in 
          <a href>, <area href>, <form action>, <frame src>,
          <iframe src>, <img src>, <input src>, <link href>
          $Response->Redirect($URL) and the first URL in 
          script tags like <script>*.location.href=$URL</script>

          These settings require that buffering be enabled, as
          Apache::ASP will parse through the buffer to parse the URLs.

          With SessionQueryParse on, it will just parse non-absolute
          URLs, but with SessionQueryParseMatch set to some server
          url regexp, like ^http://localhost , will also parse
          in the session id for URLs that match that.

lib/Apache/ASP/Response.pm  view on Meta::CPAN

use Data::Dumper qw(DumperX);
use bytes;

@Members = qw( Buffer Clean ContentType Expires ExpiresAbsolute Status );

# used for session id auto parsing
%LinkTags = (
	     'a' => 'href',
	     'area' => 'href',
	     'form' => 'action',
	     'frame' => 'src',
	     'iframe' => 'src',
	     'img' => 'src',
	     'input' => 'src',
	     'link' => 'href',
	    );

$TextHTMLRegexp = '^text/html(;|$)';

sub new {
    my $asp = shift;

site/articles/perlmonth3_tune.html  view on Meta::CPAN

requirements of SDBM_File, each time $Session is read from
or written to, it is freshly tied to the 
database and locked, so to avoid these ties can save much.
<p>
The reason why SessionSerialize is not enabled
by default is that one could easily deny service
to a user with a long running script, such that no
other scripts for that same user $Session could be run,
and this requires some expertise.
Also SessionSerialize is probably not a good thing 
for framed sites, where there is greater concurrency 
for the same $Session.



<center>
<p>
<table border=0 bgcolor=gray>

<tr bgcolor=white>
<td><b>Hits/sec</b></td>

site/changes.html  view on Meta::CPAN


 -StatINC &amp; StatINCMatch will not undef Fnctl.pm flock 
  functions constants like O_RDWR, because the code references
  are not well trackable.  This would result in sporadic 500 server
  errors when a changed module was reloaded that imported O_* flock 
  functions from Fnctl.

 +SessionQueryParse &amp; SessionQueryParseMatch
  settings that enable auto parsing session ids into 
  URLs for cookieless sessions.  Will pick up URLs in 
  &lt;a href&gt;, &lt;area href&gt;, &lt;form action&gt;, &lt;frame src&gt;,
  &lt;iframe src&gt;, &lt;img src&gt;, &lt;input src&gt;, &lt;link href&gt;
  $Response-&gt;Redirect($URL) and the first URL in 
  script tags like &lt;script&gt;*.location.href=$URL&lt;/script&gt;

  These settings require that buffering be enabled, as
  Apache::ASP will parse through the buffer to parse the URLs.

  With SessionQueryParse on, it will just parse non-absolute
  URLs, but with SessionQueryParseMatch set to some server
  url regexp, like ^<tt>http://localhost</tt> , will also parse
  in the session id for URLs that match that.

site/objects.html  view on Meta::CPAN

XSLTParser setting, which can also use XML::Sablotron ( support added in 2.11 ), 
and XML::LibXSLT ( support added in 2.29 ). 
Please see the <a href=config.html><font size=-1 face=verdana><b>CONFIG</b></font></a> section for more information on the 
XSLT* settings that drive this API.  The XSLT setting itself 
uses this API internally to do its rendering.
<font face="courier new" size=3><pre>
</pre></font>This API was created to allow developers easy XSLT component
rendering without having to render the entire ASP scripts
via XSLT.  This will make an easy plugin architecture for
those looking to integrate XML into their existing ASP
application frameworks.
<font face="courier new" size=3><pre>
</pre></font>At some point, the API will likely take files as arguments,
but not as of the 2.11 release.</font>
	

</font>
</td>

<td bgcolor=white valign=top>
&nbsp;

site/todo.html  view on Meta::CPAN


</td>



<td valign=top bgcolor=white>
<font size=+0 face=verdana,arial>

<font face=verdana><font class=title size=+1 color=#555555><b>TODO</b></font>
<font face="courier new" size=3><pre>
</pre></font>There is no specific time frame in which these things will be 
implemented.  Please let me know if any of these is of particular
interest to you, and I will give it higher priority.</font>
	<p>
	<a name=WILL%20BE%20DONE7c02ac9b></a>
	<font face=verdana><font class=title size=+0 color=#555555><b>WILL BE DONE </b></font>
<font face="courier new" size=3><pre>
 + Database storage of $Session &amp; $Application, so web clusters 
   may scale better than the current NFS/CIFS StateDir implementation
   allows, maybe via Apache::Session.
</pre></font>

t/session_query_parse.t  view on Meta::CPAN

    (
     UseStrict => 1, 
     SessionQueryParse => 1,
     Global => 'null',
     );
my $header = $r->test_header_out;
my $body = $r->test_body_out;

my @tests = (
	     '<a href="/somelink.asp?test1=value1&amp;test2=value2&amp;session-id=',
	     "<frame src='somelink.asp?test3=value3&amp;test4=value4&amp;session-id=",
	     "<form action=/somelink.asp?test5=value5&amp;test6=value6&amp;session-id="
	     );

for my $test ( @tests ) {
    $test =~ s/(\W)/\\$1/isg;
    if($body =~ /$test/s) {
	$t->ok;
    } else {
	$t->not_ok;
    }
}

$t->done;

__END__

<a href="/somelink.asp?test1=value1&amp;test2=value2">Some Link</a>

<frame src='<%= $Server->URL("somelink.asp?test3=value3", { test4 => "value4" }) %>'>

<form action=/somelink.asp?test5=value5&test6=value6>



( run in 0.809 second using v1.01-cache-2.11-cpan-df04353d9ac )