line |
stmt |
bran |
cond |
sub |
pod |
time |
code |
1
|
|
|
|
|
|
|
package Bigtop::Backend::CGI; |
2
|
|
|
|
|
|
|
|
3
|
1
|
|
|
1
|
|
6
|
use Bigtop::Keywords; |
|
1
|
|
|
|
|
5
|
|
|
1
|
|
|
|
|
84
|
|
4
|
|
|
|
|
|
|
|
5
|
|
|
|
|
|
|
BEGIN { |
6
|
1
|
|
|
1
|
|
6
|
Bigtop::Parser->add_valid_keywords( |
7
|
|
|
|
|
|
|
Bigtop::Keywords->get_docs_for( 'app', 'location' ) |
8
|
|
|
|
|
|
|
); |
9
|
|
|
|
|
|
|
|
10
|
1
|
|
|
|
|
4
|
Bigtop::Parser->add_valid_keywords( |
11
|
|
|
|
|
|
|
Bigtop::Keywords->get_docs_for( |
12
|
|
|
|
|
|
|
'controller', |
13
|
|
|
|
|
|
|
qw( location rel_location ) |
14
|
|
|
|
|
|
|
) |
15
|
|
|
|
|
|
|
); |
16
|
|
|
|
|
|
|
|
17
|
1
|
|
|
|
|
4
|
Bigtop::Parser->add_valid_keywords( |
18
|
|
|
|
|
|
|
Bigtop::Keywords->get_docs_for( 'app_literal', 'PerlTop' ) |
19
|
|
|
|
|
|
|
); |
20
|
|
|
|
|
|
|
} |
21
|
|
|
|
|
|
|
|
22
|
|
|
|
|
|
|
1; |
23
|
|
|
|
|
|
|
|
24
|
|
|
|
|
|
|
=head1 NAME |
25
|
|
|
|
|
|
|
|
26
|
|
|
|
|
|
|
Bigtop::Backend::CGI - defines the legal keywords for cgi backends |
27
|
|
|
|
|
|
|
|
28
|
|
|
|
|
|
|
=head1 SYNOPYSIS |
29
|
|
|
|
|
|
|
|
30
|
|
|
|
|
|
|
If you are making a cgi generating backend: |
31
|
|
|
|
|
|
|
|
32
|
|
|
|
|
|
|
use Bigtop::Backend::CGI |
33
|
|
|
|
|
|
|
|
34
|
|
|
|
|
|
|
This specifies the keywords for cgi generating backends. |
35
|
|
|
|
|
|
|
|
36
|
|
|
|
|
|
|
If you need to add a keyword which is generally useful, add it here |
37
|
|
|
|
|
|
|
(and send in a patch). If you need a backend specific keyword, register |
38
|
|
|
|
|
|
|
is within your backend module. |
39
|
|
|
|
|
|
|
|
40
|
|
|
|
|
|
|
=head1 DESCRIPTION |
41
|
|
|
|
|
|
|
|
42
|
|
|
|
|
|
|
If you are using a Bigtop backend in the CGI family, you should |
43
|
|
|
|
|
|
|
read this document to find out what the valid keywords are and what |
44
|
|
|
|
|
|
|
effect they have. |
45
|
|
|
|
|
|
|
|
46
|
|
|
|
|
|
|
If you are writing a Bigtop::CGI:: module, you should use this |
47
|
|
|
|
|
|
|
module. That will register the keywords your module will need. |
48
|
|
|
|
|
|
|
|
49
|
|
|
|
|
|
|
=head1 BASIC STRUCTURE |
50
|
|
|
|
|
|
|
|
51
|
|
|
|
|
|
|
A bigtop file looks like this: |
52
|
|
|
|
|
|
|
|
53
|
|
|
|
|
|
|
config { |
54
|
|
|
|
|
|
|
} |
55
|
|
|
|
|
|
|
app name { |
56
|
|
|
|
|
|
|
controller name { |
57
|
|
|
|
|
|
|
} |
58
|
|
|
|
|
|
|
} |
59
|
|
|
|
|
|
|
|
60
|
|
|
|
|
|
|
=head1 KEYWORDS |
61
|
|
|
|
|
|
|
|
62
|
|
|
|
|
|
|
Inside the app braces, you can include the location keyword. Its value will |
63
|
|
|
|
|
|
|
be the base Apache Location for the application. The default is '/'. |
64
|
|
|
|
|
|
|
|
65
|
|
|
|
|
|
|
Inside the controller braces, you may include a location or |
66
|
|
|
|
|
|
|
a rel_location keyword. Use location if you want to specify an absolute |
67
|
|
|
|
|
|
|
path and rel_location if you want to specify a path relative to the |
68
|
|
|
|
|
|
|
app level location. |
69
|
|
|
|
|
|
|
|
70
|
|
|
|
|
|
|
=head1 AUTHOR |
71
|
|
|
|
|
|
|
|
72
|
|
|
|
|
|
|
Phil Crow |
73
|
|
|
|
|
|
|
|
74
|
|
|
|
|
|
|
=head1 COPYRIGHT and LICENSE |
75
|
|
|
|
|
|
|
|
76
|
|
|
|
|
|
|
Copyright (C) 2005 by Phil Crow |
77
|
|
|
|
|
|
|
|
78
|
|
|
|
|
|
|
This library is free software; you can redistribute it and/or modify |
79
|
|
|
|
|
|
|
it under the same terms as Perl itself, either Perl version 5.8.6 or, |
80
|
|
|
|
|
|
|
at your option, any later version of Perl 5 you may have available. |
81
|
|
|
|
|
|
|
|
82
|
|
|
|
|
|
|
=cut |