2 use base qw(Class::Accessor::Fast Class::Data::Inheritable);
3 use UNIVERSAL::require;
7 use Maypole::Constants;
11 our $VERSION = '2.11';
13 # proposed privacy conventions:
14 # - no leading underscore - public to custom application code and plugins
15 # - single leading underscore - private to the main Maypole stack - *not*
17 # - double leading underscore - private to the current package
21 Maypole - MVC web application framework
25 The canonical example used in the Maypole documentation is the beer database:
31 # choose a frontend, initialise the config object, and load a plugin
32 use Maypole::Application qw/Relationship/;
34 # get the empty config object created by Maypole::Application
35 my $config = __PACKAGE__->config;
38 $config->uri_base("http://localhost/beerdb");
39 $config->template_root("/path/to/templates");
40 $config->rows_per_page(10);
41 $config->display_tables([qw[beer brewery pub style]]);
44 $config->relationships([
45 "a brewery produces beers",
46 "a style defines beers",
47 "a pub has beers on handpumps",
51 BeerDB::Brewery->untaint_columns( printable => [qw/name notes url/] );
52 BeerDB::Pub->untaint_columns( printable => [qw/name notes url/] );
53 BeerDB::Style->untaint_columns( printable => [qw/name notes/] );
54 BeerDB::Beer->untaint_columns(
55 printable => [qw/abv name price notes/],
56 integer => [qw/style brewery score/],
61 __PACKAGE__->setup("dbi:SQLite:t/beerdb.db");
67 This documents the Maypole request object. See the L<Maypole::Manual>, for a
68 detailed guide to using Maypole.
70 Maypole is a Perl web application framework similar to Java's struts. It is
71 essentially completely abstracted, and so doesn't know anything about
72 how to talk to the outside world.
74 To use it, you need to create a driver package which represents your entire
75 application. This is the C<BeerDB> package used as an example in the manual.
77 This needs to first use L<Maypole::Application> which will make your package
78 inherit from the appropriate platform driver such as C<Apache::MVC> or
79 C<CGI::Maypole>. Then, the driver calls C<setup>. This sets up the model classes
80 and configures your application. The default model class for Maypole uses
81 L<Class::DBI> to map a database to classes, but this can be changed by altering
82 configuration (B<before> calling setup.)
85 =head1 DOCUMENTATION AND SUPPORT
87 Note that some details in some of these resources may be out of date.
91 =item The Maypole Manual
93 The primary documentation is the Maypole manual. This lives in the
94 C<Maypole::Manual> pod documents included with the distribution.
98 Individual packages within the distribution contain (more or less) detailed
99 reference documentation for their API.
103 There are two mailing lists - maypole-devel and maypole-users - see
104 http://maypole.perl.org/?MailingList
106 =item The Maypole Wiki
108 The Maypole wiki provides a useful store of extra documentation -
109 http://maypole.perl.org
111 In particular, there's a FAQ (http://maypole.perl.org/?FAQ) and a cookbook
112 (http://maypole.perl.org/?Cookbook). Again, certain information on these pages
115 =item Web applications with Maypole
117 A tutorial written by Simon Cozens for YAPC::EU 2005 -
118 http://www.droogs.org/perl/maypole/maypole-tutorial.pdf [228KB].
120 =item A Database-Driven Web Application in 18 Lines of Code
122 By Paul Barry, published in Linux Journal, March 2005.
124 http://www.linuxjournal.com/article/7937
126 "From zero to Web-based database application in eight easy steps".
128 Maypole won a 2005 Linux Journal Editor's Choice Award
129 (http://www.linuxjournal.com/article/8293) after featuring in this article.
131 =item Build Web apps with Maypole
133 By Simon Cozens, on IBM's DeveloperWorks website, May 2004.
135 http://www-128.ibm.com/developerworks/linux/library/l-maypole/
137 =item Rapid Web Application Deployment with Maypole
139 By Simon Cozens, on O'Reilly's Perl website, April 2004.
141 http://www.perl.com/pub/a/2004/04/15/maypole.html
145 Some notes written by Simon Cozens. A little bit out of date, but still
146 very useful: http://www.droogs.org/perl/maypole/authentication.html
150 There's a refcard for the Maypole (and Class::DBI) APIs on the wiki -
151 http://maypole.perl.org/?CheatSheet. Probably a little out of date now - it's a
152 wiki, so feel free to fix any errors!
154 =item Plugins and add-ons
156 There are a large and growing number of plugins and other add-on modules
157 available on CPAN - http://search.cpan.org/search?query=maypole&mode=module
161 You can find a range of useful Maypole links, particularly to several thoughtful
162 blog entries, starting here: http://del.icio.us/search/?all=maypole
166 There are a couple of short reviews here:
167 http://cpanratings.perl.org/dist/Maypole
173 A couple of demos are available, sometimes with source code and configs.
177 =item http://maypole.perl.org/beerdb/
179 The standard BeerDB example, using the TT factory templates supplied in the
182 =item beerdb.riverside-cms.co.uk
184 The standard BeerDB example, running on Mason, using the factory templates
185 supplied in the L<MasonX::Maypole> distribution.
187 =item beerfb.riverside-cms.co.uk
189 A demo of L<Maypole::FormBuilder>. This site is running on the set of Mason
190 templates included in the L<Maypole::FormBuilder> distribution. See the
191 synopsis of L<Maypole::Plugin::FormBuilder> for an example driver
197 __PACKAGE__->mk_classdata($_) for qw( config init_done view_object );
199 __PACKAGE__->mk_accessors(
200 qw( params query objects model_class template_args output path
201 args action template error document_encoding content_type table
202 headers_in headers_out stash session)
205 __PACKAGE__->config( Maypole::Config->new() );
207 __PACKAGE__->init_done(0);
209 =head1 HOOKABLE METHODS
211 As a framework, Maypole provides a number of B<hooks> - methods that are
212 intended to be overridden. Some of these methods come with useful default
213 behaviour, others do nothing by default. Hooks include:
239 sub My::App::debug {1}
241 Returns the debugging flag. Override this in your application class to
242 enable/disable debugging.
244 You can also set the C<debug> flag via L<Maypole::Application>.
252 Returns the L<Maypole::Config> object
256 My::App->setup($data_source, $user, $password, \%attr);
258 Initialise the Maypole application and plugins and model classes - see
259 L<Maypole::Manual::Plugins>.
261 If your model is based on L<Maypole::Model::CDBI>, the C<\%attr> hashref can
262 contain options that are passed directly to L<Class::DBI::Loader>, to control
263 how the model hierarchy is constructed.
265 Your application should call this B<after> setting up configuration data via
274 $class->setup_model(@_);
279 Called by C<setup>. This method builds the Maypole model hierarchy.
281 A likely target for over-riding, if you need to build a customised model.
283 This method also ensures any code in custom model classes is loaded, so you
284 don't need to load them in the driver.
292 $class = ref $class if ref $class;
294 my $config = $class->config;
296 $config->model || $config->model('Maypole::Model::CDBI');
298 $config->model->require or die sprintf
299 "Couldn't load the model class %s: %s", $config->model, $@;
301 # among other things, this populates $config->classes
302 $config->model->setup_database($config, $class, @_);
304 foreach my $subclass ( @{ $config->classes } )
307 unshift @{ $subclass . "::ISA" }, $config->model;
309 # Load custom model code, if it exists - nb this must happen after the
310 # unshift, to allow code attributes to work, but before adopt(),
311 # in case adopt() calls overridden methods on $subclass
312 $class->load_model_subclass($subclass);
314 $config->model->adopt($subclass) if $config->model->can("adopt");
316 # eval "use $subclass";
317 # die "Error loading $subclass: $@"
318 # if $@ and $@ !~ /Can\'t locate \S+ in \@INC/;
322 =item load_model_subclass($subclass)
324 This method is called from C<setup_model()>. It attempts to load the
325 C<$subclass> package, if one exists. So if you make a customized C<BeerDB::Beer>
326 package, you don't need to explicitly load it.
328 If, perhaps during development, you don't want to load up custom classes, you
329 can override this method and load them manually.
333 sub load_model_subclass
335 my ($class, $subclass) = @_;
337 my $config = $class->config;
339 # Load any external files for the model base class or subclasses
340 # (e.g. BeerDB/DBI.pm or BeerDB/Beer.pm) based on code borrowed from
341 # Maypole::Plugin::Loader and Class::DBI.
342 if ( $subclass->require )
344 warn "Loaded external module for '$subclass'\n" if $class->debug > 1;
348 (my $filename = $subclass) =~ s!::!/!g;
349 die "Loading '$subclass' failed: $@\n"
350 unless $@ =~ /Can\'t locate \Q$filename\E\.pm/;
351 warn "Did not find external module for '$subclass'\n"
352 if $class->debug > 1;
358 Loads the view class and instantiates the view object.
360 You should not call this directly, but you may wish to override this to add
361 application-specific initialisation - see L<Maypole::Manual::Plugins>.
368 my $config = $class->config;
369 $config->view || $config->view("Maypole::View::TT");
370 $config->view->require;
371 die "Couldn't load the view class " . $config->view . ": $@" if $@;
372 $config->display_tables
373 || $config->display_tables( $class->config->tables );
374 $class->view_object( $class->config->view->new );
375 $class->init_done(1);
380 Constructs a very minimal new Maypole request object.
390 config => $class->config,
398 Get/set the Maypole::View object
402 =head1 INSTANCE METHODS
410 This method sets up the class if it's not done yet, sets some defaults and
411 leaves the dirty work to C<handler_guts>.
415 # handler() has a method attribute so that mod_perl will invoke
416 # BeerDB->handler() as a method rather than a plain function
417 # BeerDB::handler() and so this inherited implementation will be
418 # found. See e.g. "Practical mod_perl" by Bekman & Cholet for
419 # more information <http://modperlbook.org/html/ch25_01.html>
422 # See Maypole::Workflow before trying to understand this.
423 my ($class, $req) = @_;
425 $class->init unless $class->init_done;
427 my $self = $class->new;
429 # initialise the request
430 $self->headers_out(Maypole::Headers->new);
431 $self->get_request($req);
432 $self->parse_location;
434 # hook useful for declining static requests e.g. images, or perhaps for
435 # sanitizing request parameters
436 my $status = $self->start_request_hook;
437 return $status unless $status == Maypole::Constants::OK();
439 $self->session($self->get_session);
441 $status = $self->handler_guts;
443 # moving this here causes unit test failures - need to check why
444 # before committing the move
445 #$status = $self->__call_process_view unless $self->output;
447 return $status unless $status == OK;
449 # TODO: require send_output to return a status code
457 This is the main request handling method and calls various methods to handle the
458 request/response and defines the workflow within Maypole.
460 B<Currently undocumented and liable to be refactored without warning>.
464 # The root of all evil
469 $self->__load_request_model;
471 my $applicable = $self->is_model_applicable;
473 $self->__setup_plain_template unless $applicable;
477 eval { $status = $self->call_authenticate };
479 if ( my $error = $@ )
481 $status = $self->call_exception($error);
485 warn "caught authenticate error: $error";
486 return $self->debug ?
487 $self->view_object->error($self, $error) : ERROR;
491 if ( $self->debug and $status != OK and $status != DECLINED )
493 $self->view_object->error( $self,
494 "Got unexpected status $status from calling authentication" );
497 return $status unless $status == OK;
499 # We run additional_data for every request
500 $self->additional_data;
504 eval { $self->model_class->process($self) };
506 if ( my $error = $@ )
508 $status = $self->call_exception($error);
512 warn "caught model error: $error";
513 return $self->debug ?
514 $self->view_object->error($self, $error) : ERROR;
519 # less frequent path - perhaps output has been set to an error message
520 return OK if $self->output;
522 # normal path - no output has been generated yet
523 return $self->__call_process_view;
526 sub __load_request_model
529 $self->model_class( $self->config->model->class_of($self, $self->table) );
532 # is_applicable() returned false, so set up a plain template. Model processing
533 # will be skipped, but need to remove the model anyway so the template can't
535 sub __setup_plain_template
539 # It's just a plain template
540 $self->model_class(undef);
542 my $path = $self->path;
543 $path =~ s{/$}{}; # De-absolutify
546 $self->template($self->path);
549 # The model has been processed or skipped (if is_applicable returned false),
550 # any exceptions have been handled, and there's no content in $self->output
551 sub __call_process_view
557 eval { $status = $self->view_object->process($self) };
559 if ( my $error = $@ )
561 $status = $self->call_exception($error);
565 warn "caught view error: $error" if $self->debug;
566 return $self->debug ?
567 $self->view_object->error($self, $error) : ERROR;
576 You should only need to define this method if you are writing a new
577 Maypole backend. It should return something that looks like an Apache
578 or CGI request object, it defaults to blank.
586 Turns the backend request (e.g. Apache::MVC, Maypole, CGI) into a Maypole
587 request. It does this by setting the C<path>, and invoking C<parse_path> and
590 You should only need to define this method if you are writing a new Maypole
597 die "parse_location is a virtual method. Do not use Maypole directly; " .
598 "use Apache::MVC or similar";
601 =item start_request_hook
603 This is called immediately after setting up the basic request. The default
604 method simply returns C<Maypole::Constants::OK>.
606 Any other return value causes Maypole to abort further processing of the
607 request. This is useful for filtering out requests for static files, e.g.
608 images, which should not be processed by Maypole or by the templating engine:
610 sub start_request_hook
614 return Maypole::Constants::DECLINED if $r->path =~ /\.jpg$/;
615 return Maypole::Constants::OK;
620 sub start_request_hook { Maypole::Constants::OK }
624 B<This method is deprecated> as of version 2.11. If you have overridden it,
625 please override C<is_model_applicable> instead, and change the return type
626 from a Maypole:Constant to a true/false value.
628 Returns a Maypole::Constant to indicate whether the request is valid.
630 =item is_model_applicable
632 Returns true or false to indicate whether the request is valid.
634 The default implementation checks that C<< $r->table >> is publicly
635 accessible and that the model class is configured to handle the
640 sub is_model_applicable
644 # cater for applications that are using obsolete version
645 if ($self->can('is_applicable'))
647 warn "DEPRECATION WARNING: rewrite is_applicable to the interface ".
648 "of Maypole::is_model_applicable\n";
649 return $self->is_applicable == OK;
652 # Establish which tables should be processed by the model
653 my $config = $self->config;
655 $config->ok_tables || $config->ok_tables( $config->display_tables );
657 $config->ok_tables( { map { $_ => 1 } @{ $config->ok_tables } } )
658 if ref $config->ok_tables eq "ARRAY";
660 my $ok_tables = $config->ok_tables;
662 # Does this request concern a table to be processed by the model?
663 my $table = $self->table;
667 if (exists $ok_tables->{$table})
674 warn "We don't have that table ($table).\n"
675 . "Available tables are: "
676 . join( ",", keys %$ok_tables )
677 if $self->debug and not $ok_tables->{$table};
682 # Is the action public?
683 my $action = $self->action;
684 return 1 if $self->model_class->is_public($action);
686 warn "The action '$action' is not applicable to the table $table"
694 The default method is empty.
700 =item call_authenticate
702 This method first checks if the relevant model class
703 can authenticate the user, or falls back to the default
704 authenticate method of your Maypole application.
708 sub call_authenticate
712 # Check if we have a model class with an authenticate() to delegate to
713 return $self->model_class->authenticate($self)
714 if $self->model_class and $self->model_class->can('authenticate');
716 # Interface consistency is a Good Thing -
717 # the invocant and the argument may one day be different things
718 # (i.e. controller and request), like they are when authenticate()
719 # is called on a model class (i.e. model and request)
720 return $self->authenticate($self);
725 Returns a Maypole::Constant to indicate whether the user is authenticated for
728 The default implementation returns C<OK>
732 sub authenticate { return OK }
737 This model is called to catch exceptions, first after authenticate, then after
738 processing the model class, and finally to check for exceptions from the view
741 This method first checks if the relevant model class
742 can handle exceptions the user, or falls back to the default
743 exception method of your Maypole application.
749 my ($self, $error) = @_;
751 # Check if we have a model class with an exception() to delegate to
752 if ( $self->model_class && $self->model_class->can('exception') )
754 my $status = $self->model_class->exception( $self, $error );
755 return $status if $status == OK;
758 return $self->exception($error);
764 This method is called if any exceptions are raised during the authentication or
765 model/view processing. It should accept the exception as a parameter and return
766 a Maypole::Constant to indicate whether the request should continue to be
771 sub exception { return ERROR }
773 =item additional_data
775 Called before the model processes the request, this method gives you a chance to
776 do some processing for each request, for example, manipulating C<template_args>.
780 sub additional_data { }
784 Sends the output and additional headers to the user.
789 die "send_output is a virtual method. Do not use Maypole directly; use Apache::MVC or similar";
797 =head2 Path processing and manipulation
803 Returns the request path
807 Parses the request path and sets the C<args>, C<action> and C<table>
808 properties. Calls C<preprocess_path> before parsing path and setting properties.
816 # Previous versions unconditionally set table, action and args to whatever
817 # was in @pi (or else to defaults, if @pi is empty).
818 # Adding preprocess_path(), and then setting table, action and args
819 # conditionally, broke lots of tests, hence this:
820 $self->$_(undef) for qw/action table args/;
822 $self->preprocess_path;
823 $self->path || $self->path('frontpage');
825 my @pi = grep {length} split '/', $self->path;
828 $self->table || $self->table(shift @pi);
829 $self->action || $self->action( shift @pi or 'index' );
830 $self->args || $self->args(\@pi);
833 =item preprocess_path
835 Sometimes when you don't want to rewrite or over-ride parse_path but
836 want to rewrite urls or extract data from them before it is parsed.
838 This method is called after parse_location has populated the request
839 information and before parse_path has populated the model and action
840 information, and is passed the request object.
842 You can set action, args or table in this method and parse_path will
843 then leave those values in place or populate them if not present
847 sub preprocess_path { };
849 =item make_path( %args or \%args or @args )
851 This is the counterpart to C<parse_path>. It generates a path to use
852 in links, form actions etc. To implement your own path scheme, just override
853 this method and C<parse_path>.
855 %args = ( table => $table,
857 additional => $additional, # optional - generally an object ID
860 \%args = as above, but a ref
862 @args = ( $table, $action, $additional ); # $additional is optional
864 C<id> can be used as an alternative key to C<additional>.
866 C<$additional> can be a string, an arrayref, or a hashref. An arrayref is
867 expanded into extra path elements, whereas a hashref is translated into a query
878 if (@_ == 1 and ref $_[0] and ref $_[0] eq 'HASH')
882 elsif ( @_ > 1 and @_ < 4 )
884 $args{table} = shift;
885 $args{action} = shift;
886 $args{additional} = shift;
893 do { die "no $_" unless $args{$_} } for qw( table action );
895 my $additional = $args{additional} || $args{id};
901 # if $additional is a href, make_uri() will transform it into a query
902 @add = (ref $additional eq 'ARRAY') ? @$additional : ($additional);
905 my $uri = $r->make_uri($args{table}, $args{action}, @add);
907 return $uri->as_string;
912 =item make_uri( @segments )
914 Make a L<URI> object given table, action etc. Automatically adds
917 If the final element in C<@segments> is a hash ref, C<make_uri> will render it
924 my ($r, @segments) = @_;
926 my $query = (ref $segments[-1] eq 'HASH') ? pop(@segments) : undef;
928 my $base = $r->config->uri_base;
931 my $uri = URI->new($base);
932 $uri->path_segments($uri->path_segments, grep {length} @segments);
934 my $abs_uri = $uri->abs('/');
935 $abs_uri->query_form($query) if $query;
941 Turns post data and query string paramaters into a hash of C<params>.
943 You should only need to define this method if you are writing a new Maypole
950 die "parse_args() is a virtual method. Do not use Maypole directly; ".
951 "use Apache::MVC or similar";
954 =item get_template_root
956 Implementation-specific path to template root.
958 You should only need to define this method if you are writing a new Maypole
959 backend. Otherwise, see L<Maypole::Config/"template_root">
963 sub get_template_root {'.'}
967 =head2 Request properties
973 Returns the perl package name that will serve as the model for the
974 request. It corresponds to the request C<table> attribute.
979 Get/set a list of model objects. The objects will be accessible in the view
982 If the first item in C<$self-E<gt>args> can be C<retrieve()>d by the model
983 class, it will be removed from C<args> and the retrieved object will be added to
984 the C<objects> list. See L<Maypole::Model> for more information.
988 $self->template_args->{foo} = 'bar';
990 Get/set a hash of template variables.
994 A place to put custom application data. Not used by Maypole itself.
998 Get/set the template to be used by the view. By default, it returns
1004 Get/set a request error
1008 Get/set the response output. This is usually populated by the view class. You
1009 can skip view processing by setting the C<output>.
1013 The table part of the Maypole request path
1017 The action part of the Maypole request path
1021 A list of remaining parts of the request path after table and action
1027 A L<Maypole::Headers> object containing HTTP headers for the request
1031 A L<HTTP::Headers> object that contains HTTP headers for the output
1033 =item document_encoding
1035 Get/set the output encoding. Default: utf-8.
1039 Get/set the output content type. Default: text/html
1043 Returns the protocol the request was made with, i.e. https
1048 die "get_protocol is a virtual method. Do not use Maypole directly; use Apache::MVC or similar";
1053 =head2 Request parameters
1055 The source of the parameters may vary depending on the Maypole backend, but they
1056 are usually populated from request query string and POST data.
1058 Maypole supplies several approaches for accessing the request parameters. Note
1059 that the current implementation (via a hashref) of C<query> and C<params> is
1060 likely to change in a future version of Maypole. So avoid direct access to these
1063 $r->{params}->{foo} # bad
1064 $r->params->{foo} # better
1066 $r->{query}->{foo} # bad
1067 $r->query->{foo} # better
1069 $r->param('foo') # best
1075 An accessor (get or set) for request parameters. It behaves similarly to
1076 CGI::param() for accessing CGI parameters, i.e.
1078 $r->param # returns list of keys
1079 $r->param($key) # returns value for $key
1080 $r->param($key => $value) # returns old value, sets to new value
1086 my ($self, $key) = (shift, shift);
1088 return keys %{$self->params} unless defined $key;
1090 return unless exists $self->params->{$key};
1092 my $val = $self->params->{$key};
1096 my $new_val = shift;
1097 $self->params->{$key} = $new_val;
1100 return ref $val ? @$val : ($val) if wantarray;
1102 return ref $val ? $val->[0] : $val;
1108 Returns a hashref of request parameters.
1110 B<Note:> Where muliple values of a parameter were supplied, the C<params> value
1111 will be an array reference.
1115 Alias for C<params>.
1119 =head3 Utility methods
1123 =item redirect_request
1125 Sets output headers to redirect based on the arguments provided
1127 Accepts either a single argument of the full url to redirect to, or a hash of
1130 $r->redirect_request('http://www.example.com/path');
1134 $r->redirect_request(protocol=>'https', domain=>'www.example.com', path=>'/path/file?arguments', status=>'302', url=>'..');
1136 The named parameters are protocol, domain, path, status and url
1138 Only 1 named parameter is required but other than url, they can be combined as
1139 required and current values (from the request) will be used in place of any
1140 missing arguments. The url argument must be a full url including protocol and
1141 can only be combined with status.
1145 sub redirect_request {
1146 die "redirect_request is a virtual method. Do not use Maypole directly; use Apache::MVC or similar";
1149 =item redirect_internal_request
1153 sub redirect_internal_request {
1158 =item make_random_id
1160 returns a unique id for this request can be used to prevent or detect repeat
1165 # Session and Repeat Submission Handling
1166 sub make_random_id {
1167 use Maypole::Session;
1168 return Maypole::Session::generate_unique_id();
1173 =head1 SEQUENCE DIAGRAMS
1175 See L<Maypole::Manual::Workflow> for a detailed discussion of the sequence of
1176 calls during processing of a request. This is a brief summary:
1180 BeerDB Maypole::Model::CDBI
1184 || setup_model | setup_database() creates
1185 ||------+ | a subclass of the Model
1186 |||<----+ | for each table
1188 ||| setup_database | |
1189 |||--------------------->|| 'create' *
1190 ||| ||----------> $subclass
1192 ||| load_model_subclass | |
1193 foreach |||------+ ($subclass) | |
1194 $subclass ||||<----+ | require |
1195 ||||--------------------------------------->|
1197 ||| adopt($subclass) | |
1198 |||--------------------->|| |
1203 || | new | view_object: e.g
1204 ||---------------------------------------------> Maypole::View::TT
1216 BeerDB Model $subclass view_object
1219 o-------->| new | | |
1220 |-----> r:BeerDB | | |
1224 | ||-----+ parse_location | | |
1227 | ||-----+ start_request_hook | | |
1230 | ||-----+ get_session | | |
1233 | ||-----+ handler_guts | | |
1235 | ||| class_of($table) | | |
1236 | |||------------------------->|| | |
1237 | ||| $subclass || | |
1238 | |||<-------------------------|| | |
1240 | |||-----+ is_model_applicable| | |
1243 | |||-----+ call_authenticate | | |
1246 | |||-----+ additional_data | | |
1248 | ||| process | | fetch_objects
1249 | |||--------------------------------->||-----+ |
1257 | |||------------------------------------------->|| template
1261 | || send_output | | |
1265 <------------------|| | | |
1276 There's more documentation, examples, and information on our mailing lists
1277 at the Maypole web site:
1279 L<http://maypole.perl.org/>
1281 L<Maypole::Application>, L<Apache::MVC>, L<CGI::Maypole>.
1285 Maypole is currently maintained by Aaron Trevena, David Baird, Dave Howorth and
1288 =head1 AUTHOR EMERITUS
1290 Simon Cozens, C<simon#cpan.org>
1292 Simon Flack maintained Maypole from 2.05 to 2.09
1294 Sebastian Riedel, C<sri#oook.de> maintained Maypole from 1.99_01 to 2.04
1298 Sebastian Riedel, Danijel Milicevic, Dave Slack, Jesse Sheidlower, Jody Belka,
1299 Marcus Ramberg, Mickael Joanne, Randal Schwartz, Simon Flack, Steve Simms,
1300 Veljko Vidovic and all the others who've helped.
1304 You may distribute this code under the same terms as Perl itself.