X-Git-Url: https://git.decadent.org.uk/gitweb/?a=blobdiff_plain;ds=sidebyside;f=lib%2FMaypole.pm;h=d0ba118a5863609d80187bf08c3e521653d65c84;hb=83e1c35229307f73d613c7e8b473abf41ba9b76a;hp=e677828c96916ad6c4dddcd8de07eba08f5d5e77;hpb=8fe02231d92e4564f0dc52a1aa00e9d0cb974819;p=maypole.git

diff --git a/lib/Maypole.pm b/lib/Maypole.pm
index e677828..d0ba118 100644
--- a/lib/Maypole.pm
+++ b/lib/Maypole.pm
@@ -219,7 +219,7 @@ for the designers to customize, and then write an Apache handler like
 this:
 
     package ProductDatabase;
-    use base 'Apache::MVC';
+    use base 'Maypole::Application';
     __PACKAGE__->set_database("dbi:mysql:products");
     ProductDatabase->config->uri_base = "http://your.site/catalogue/";
     ProductDatabase::Product->has_a("category" => ProductDatabase::Category); 
@@ -303,7 +303,8 @@ You should probably not use Maypole directly. Maypole is an abstract
 class which does not specify how to communicate with the outside world.
 The most popular subclass of Maypole is L<Apache::MVC>, which interfaces
 the Maypole framework to Apache mod_perl; another important one is
-L<CGI::Maypole>.
+L<CGI::Maypole>. However, if you just don't care, use Maypole::Application,
+and it will choose the right one for you.
 
 If you are implementing Maypole subclasses, you need to provide at least
 the C<parse_location> and C<send_output> methods. You may also want to
@@ -329,7 +330,7 @@ There's more documentation, examples, and a wiki at the Maypole web site:
 
 http://maypole.simon-cozens.org/
 
-L<Apache::MVC>, L<CGI::Maypole>.
+L<Maypole::Application>,L<Apache::MVC>, L<CGI::Maypole>.
 
 =head1 MAINTAINER