You are viewing a plain text version of this content. The canonical link for it is here.
Posted to docs-cvs@perl.apache.org by st...@apache.org on 2002/04/21 09:42:35 UTC

cvs commit: modperl-docs/src/start/tips registry.html

stas        02/04/21 00:42:35

  Added:       src/jobs .cvsignore jobs.html
               src/start .cvsignore LICENSE.txt about.html config.cfg
               src/start/tips registry.html
  Removed:     src/about LICENSE.txt about.html jobs.html
               src/about/tips registry.html
  Log:
  move the about pages into a new 'start' docset,
  move jobs in jobs dir (may be will become a docset in the future)
  
  Revision  Changes    Path
  1.1                  modperl-docs/src/jobs/.cvsignore
  
  Index: .cvsignore
  ===================================================================
  cache.*.dat
  
  
  1.1                  modperl-docs/src/jobs/jobs.html
  
  Index: jobs.html
  ===================================================================
  <html>
    <head>
      <meta name="Description" content="Find the mod_perl job of your dreams!">
      <title>Jobs</title>
    </head>
  <body bgcolor="#ffffff">
  
  <p>To submit jobs, see more Perl jobs and search the job listings go to
  <a href="http://jobs.perl.org/">The Perl Job site</a>.</p>
  
  <p>(Note: The jobs listing is fetched from a remote site using
  JavaScript, so it may take a while before it gets
  downloaded. Alternatively go directly to <a
  href="http://jobs.perl.org/search?q=mod_perl"">the search results</a>.)</p>
  
  <script language="JavaScript" type="text/javascript" 
  src="http://jobs.perl.org/rss/mod_perl.js?limit=25;details=1"></script>
  
  <!-- cannot use noscript, as it breaks layout in NS4 :( -->
  
  </body>
  </html>
  
  
  
  1.1                  modperl-docs/src/start/.cvsignore
  
  Index: .cvsignore
  ===================================================================
  cache.*.dat
  
  
  1.1                  modperl-docs/src/start/LICENSE.txt
  
  Index: LICENSE.txt
  ===================================================================
  /* ====================================================================
   * The Apache Software License, Version 1.1
   *
   * Copyright (c) 2000 The Apache Software Foundation.  All rights
   * reserved.
   *
   * Redistribution and use in source and binary forms, with or without
   * modification, are permitted provided that the following conditions
   * are met:
   *
   * 1. Redistributions of source code must retain the above copyright
   *    notice, this list of conditions and the following disclaimer.
   *
   * 2. Redistributions in binary form must reproduce the above copyright
   *    notice, this list of conditions and the following disclaimer in
   *    the documentation and/or other materials provided with the
   *    distribution.
   *
   * 3. The end-user documentation included with the redistribution,
   *    if any, must include the following acknowledgment:
   *       "This product includes software developed by the
   *        Apache Software Foundation (http://www.apache.org/)."
   *    Alternately, this acknowledgment may appear in the software itself,
   *    if and wherever such third-party acknowledgments normally appear.
   *
   * 4. The names "Apache" and "Apache Software Foundation" must
   *    not be used to endorse or promote products derived from this
   *    software without prior written permission. For written
   *    permission, please contact apache@apache.org.
   *
   * 5. Products derived from this software may not be called "Apache",
   *    nor may "Apache" appear in their name, without prior written
   *    permission of the Apache Software Foundation.
   *
   * THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED
   * WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
   * OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
   * DISCLAIMED.  IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR
   * ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
   * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
   * LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
   * USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
   * ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
   * OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT
   * OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
   * SUCH DAMAGE.
   * ====================================================================
   *
   * This software consists of voluntary contributions made by many
   * individuals on behalf of the Apache Software Foundation.  For more
   * information on the Apache Software Foundation, please see
   * <http://www.apache.org/>.
   *
   * Portions of this software are based upon public domain software
   * originally written at the National Center for Supercomputing Applications,
   * University of Illinois, Urbana-Champaign.
   */
  
  
  
  
  1.1                  modperl-docs/src/start/about.html
  
  Index: about.html
  ===================================================================
  <html>
  <head>
      <title>What is mod_perl?</title> 
      <meta name="Description" content="Apache + Perl = mod_perl">
  </head>
  <body bgcolor="white">
  
  <h1>mod_perl is the marriage of Apache and Perl</h1>
  
  mod_perl brings together two of the most powerful and mature
  technologies available to the web professional today.
  
  <br><br>
  
  Simply <a href="../download/">install</a> mod_perl
  and you have the <b>full power</b> of the <a href="http://httpd.apache.org">Apache Web Server</a>
  at your fingertips:
  
  
  <blockquote>
  
      <br><br>
  
      <b>Accelerate your existing dynamic content</b>
          <blockquote>
  
              The standard Apache::Registry module can provide 100x speedups for your
              existing CGI scripts and reduce the load on your server at the same
              time. A few changes to the web server's config is all that is required
              to run your existing CGI scripts at lightning speed.
              <a class="more" href="tips/registry.html">more &#187;</a>
          </blockquote>
  
      <br><br>
  
      <b>Easily create custom modules that become part of Apache</b>
          <blockquote>
              With the power of Perl, writing custom modules to extend and
              enhance Apache is a snap.  Content handlers can be written in just
              a few lines of code and can be quickly integrated with existing
              modules specifically designed for use with mod_perl, or with
              modules freely available from the <a href="http://cpan.org">CPAN</a>.
          </blockquote>
              
          
  
      <br><br>
      
      <b>Gain access to all request stages</b>
          <blockquote>
              mod_perl is not only about super fast content generation.
              With mod_perl all phases of the request cycle can be accessed
              and controlled.  No other web acceleration product gives you this
              much control.
  
              <br><br>
              Imagine the power of mod_rewrite combined with the power of Perl!
              Rewrite URLs based on the content of a directory structure, settings
              stored in a relational database, or the phase of the moon.
  
              <br><br>
              Write custom authentication and authorization modules to integrate with
              existing user databases or take advantage of the well-supported CPAN
              modules to extend the abilities of Apache. You can even create custom
              logging tailored to your site's specific needs. 
          </blockquote>
  
      <br><br>
              
      <b>Configure Apache with Perl</b>
          <blockquote>
              Perl can be used right in your httpd.conf file.  Apache can be dynamically
              configured during startup.  Everything from virtual hosts to authentication
              settings can be configured via Perl.  URL translation logic can be added right
              in your httpd.conf file.  Settings can be adjusted on a per-request basis and
              values passed from code in httpd.conf to your content generation modules.
              You can even generate complete HTTP output from the httpd.conf configuration file.
          </blockquote>
  
  
      <br><br>
  
      <b>Install Third-party modules</b>
          <blockquote>
              Third-party modules give you application functionality such as
              <b>sessions</b>, <b>passwords</b> and <b>database integration</b>.
          </blockquote>
  
      <br><br>
  
      <b>Application Frameworks</b>
          <blockquote>
              There are many high-level packages built on top of the mod_perl infrastructure
              to help you develop scalable and easily managed dynamic sites.
              All are well supported and maintain a loyal group of users.
              <br><br>
              You can select from a number of templating systems or application frameworks
              for use with mod_perl.
              See the mod_perl <a href="../products/app-server.html">Products</a> section for more
              information.
          </blockquote>
  
  
      <br><br>
          
      <b>Apache 2.0 support</b>
          <blockquote>
              With mod_perl you can take advantage of the features of Apache 2.0.
              For example, custom protocol handlers can be written in Perl.
          </blockquote>
  
      <br><br>
  
      <b>Active Support Community</b>
          <blockquote>
              mod_perl has all the support anyone could ask for.
              <br><br>
              Response time to questions posted on any of the mod_perl related
              <a href="../maillist/index.html">lists</a> is often minutes.  And
              with such a large installed base there's often someone that knows
              the answer to your specific question.
              In addition, a wealth of well maintained documentation is
              available online through this web site.
              For off-line, spend your time with execelent
              <a href="../docs/offsite/books.html">books</a> about mod_perl.
              There's nothing like curling up in bed with a good book.  Or someone that's read one.
          </blockquote>
              
  
  </blockquote>
  <br><br>
  Now, it's time to <a href="../docs/1.0/guide/getwet.html">Get Your Feet Wet</a> with <b>mod_perl</b>.
  
  
  
  
  <h1>License</h1>
  
  <p>Like all Apache Software Foundation projects, mod_perl is licensed
  under <a href="LICENSE.txt">The Apache License</a>.</p>
  
  
  </body>
  </html>
  
  
  
  1.1                  modperl-docs/src/start/config.cfg
  
  Index: config.cfg
  ===================================================================
  use vars qw(@c);
  @c = (
  
      id => 'start',
  
      title => "What is mod_perl",
  
      abstract => <<EOB,
  EOB
      
       chapters => [
           qw(
              about.html
              tips/registry.html
             )
       ],
  
       # non-pod/html files or dirs to be copied unmodified
       copy_glob => [
           qw(
              LICENSE.txt
             )
       ],
  
  );
  
  
  
  1.1                  modperl-docs/src/start/tips/registry.html
  
  Index: registry.html
  ===================================================================
  <html>
  <head>
      <title>Apache::Registry Example</title> 
      <meta name="Description" content="Apache::Registry Example">
  </head>
  <body bgcolor="white">
  
  
  <h1>Running CGI scripts with mod_perl</h1>
  
  Existing CGI scripts will run much faster under mod_perl.
  And converting existing CGI scripts to run under mod_perl is easy.
  
  For example, here's an existing CGI script called <tt>hello.cgi</tt>.
  
  <pre>
      #!/usr/local/bin/perl -w
      use strict;
      use CGI;
      my $q = CGI->new;
      print $q->header,
            $q->start_html,
            $q->h1('Hello World!'),
            $q->end_html;
  </pre>
  
  This script can now be run as-is under Apache::Registry by using the
  following configuration in httpd.conf:
  
  <pre>
      &lt;files hello.cgi&gt;
          SetHandler perl-script
          PerlHandler Apache::Registry
          Options ExecCGI
      &lt;/files&gt;
  </pre>
  
  <p>
  That's basically it.  Your scripts do need to be well coded, but there's even the
  Apache::PerlRun module to help with those "less clean" programs.
  <p>
  For more information on running CGI scripts under mod_perl please see <a href="../../docs/1.0/faqs/index.html">mod_perl FAQs</a>.
  
  
  </body>
  </html>
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-cvs-unsubscribe@perl.apache.org
For additional commands, e-mail: docs-cvs-help@perl.apache.org