stas 2002/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 Changes Path
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 -0000 1.10
+++ modules.pod 13 Nov 2002 15:18:33 -0000 1.11
@@ -268,8 +268,12 @@
=head1 Apache::RegistryNG -- Apache::Registry New Generation
C<Apache::RegistryNG> is the same as C<Apache::Registry>, 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<Apache::RegistryNG> uses an Object Oriented interface.
PerlModule Apache::RegistryNG
<Location /perl>
@@ -287,7 +291,8 @@
There is no compelling reason to use C<Apache::RegistryNG> over
C<Apache::Registry>, unless you want to do add or change the
-functionality of the existing I<Registry.pm>. For example,
+functionality of the existing I<Registry.pm> or if you want to use
+filenames instead of URIs for namespaces. For example,
C<Apache::RegistryBB> (Bare-Bones) is another subclass that skips the
stat() call performed by C<Apache::Registry> on each request.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
