cvs commit: modperl-docs/src/docs/1.0/guide modules.pod

[stas]

stas2002/11/13 07:18:33

  Modified:src/docs/1.0/guide modules.pod
  Log:
  stress the filename vs. URI package name in RegistryNG, thanks to
  Nicholas Oxhøj for asking for that.
  
  Revision  ChangesPath
  1.11  +8 -3  modperl-docs/src/docs/1.0/guide/modules.pod
  
  Index: modules.pod
  ===
  RCS file: /home/cvs/modperl-docs/src/docs/1.0/guide/modules.pod,v
  retrieving revision 1.10
  retrieving revision 1.11
  diff -u -r1.10 -r1.11
  --- modules.pod   8 Nov 2002 06:34:47 -   1.10
  +++ modules.pod   13 Nov 2002 15:18:33 -  1.11
  @@ -268,8 +268,12 @@
   =head1 Apache::RegistryNG -- Apache::Registry New Generation
   
   C is the same as C, aside from
  -using filenames instead of URIs for namespaces.  It also uses an Object 
  -Oriented interface.
  +using filenames instead of URIs for namespaces.  This feature ensures
  +that if the same CGI script is requested from different URIs
  +(e.g. different hostnames) it'll be compiled and cached only once,
  +thus saving memory.
  +
  +C uses an Object Oriented interface.
   
 PerlModule Apache::RegistryNG
 
  @@ -287,7 +291,8 @@
   
   There is no compelling reason to use C over
   C, unless you want to do add or change the
  -functionality of the existing I.  For example,
  +functionality of the existing I or if you want to use
  +filenames instead of URIs for namespaces.  For example,
   C (Bare-Bones) is another subclass that skips the
   stat() call performed by C on each request.
   
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: modperl-docs/src/docs/2.0/user/config config.pod

[stas]

stas2002/11/13 07:43:34

  Modified:src/docs/2.0/devel/porting porting.pod
   src/docs/2.0/user/config config.pod
  Log:
  a few minor corrections
  
  Revision  ChangesPath
  1.2   +9 -9  modperl-docs/src/docs/2.0/devel/porting/porting.pod
  
  Index: porting.pod
  ===
  RCS file: /home/cvs/modperl-docs/src/docs/2.0/devel/porting/porting.pod,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- porting.pod   13 Aug 2002 11:46:21 -  1.1
  +++ porting.pod   13 Nov 2002 15:43:34 -  1.2
  @@ -65,16 +65,16 @@
   
   to your module. You can also use the variable C<$mod_perl::VERSION>.
   
  -In the configuration file you can use a special configuration define
  -C which is enabled internally, as if the server had been
  -started with C<-DMODPERL2>.
  +In the configuration file you can use a special configuration "define"
  +symbol C which is enabled internally, as if the server had
  +been started with C<-DMODPERL2>.
   
  - 
  - # 2.0 configuration
  - 
  - 
  - # else
  - 
  +  
  +  # 2.0 configuration
  +  
  +  
  +  # else
  +  
   
   From within Perl code this can be tested with
   C, for example:
  
  
  
  1.26  +10 -10modperl-docs/src/docs/2.0/user/config/config.pod
  
  Index: config.pod
  ===
  RCS file: /home/cvs/modperl-docs/src/docs/2.0/user/config/config.pod,v
  retrieving revision 1.25
  retrieving revision 1.26
  diff -u -r1.25 -r1.26
  --- config.pod3 Sep 2002 05:32:59 -   1.25
  +++ config.pod13 Nov 2002 15:43:34 -  1.26
  @@ -245,7 +245,7 @@
   
   =item *
   
  -C and C get tied to the request object C<$r>, which
  +C and C get tied to the request object C<$r>, which
   makes possible to read from C and print directly to C
   via C, instead of implicit calls like
   C<$r-Eputs()>.
  @@ -823,18 +823,18 @@
   
   =head2 MODPERL2 Define Option
   
  -When running under mod_perl 2.0 a special configuration define
  -C is enabled internally, as if the server had been started
  -with C<-DMODPERL2>. For example this can be used to write a
  +When running under mod_perl 2.0 a special configuration "define"
  +symbol C is enabled internally, as if the server had been
  +started with C<-DMODPERL2>. For example this can be used to write a
   configuration file which needs to do something different whether it's
   running under mod_perl 1.0 or 2.0:
   
  - 
  - # 2.0 configuration
  - 
  - 
  - # else
  - 
  +  
  +  # 2.0 configuration
  +  
  +  
  +  # else
  +  
   
   From within Perl code this can be tested with
   C, for example:
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]