line |
stmt |
bran |
cond |
sub |
pod |
time |
code |
1
|
|
|
|
|
|
|
|
2
|
|
|
|
|
|
|
our $VERSION = '1.0.2'; |
3
|
|
|
|
|
|
|
|
4
|
|
|
|
|
|
|
use Google::RestApi::Setup; |
5
|
1
|
|
|
1
|
|
435
|
|
|
1
|
|
|
|
|
3
|
|
|
1
|
|
|
|
|
7
|
|
6
|
|
|
|
|
|
|
|
7
|
252
|
|
|
252
|
0
|
922
|
1; |
8
|
0
|
|
|
0
|
0
|
|
|
9
|
|
|
|
|
|
|
|
10
|
|
|
|
|
|
|
=head1 NAME |
11
|
|
|
|
|
|
|
|
12
|
|
|
|
|
|
|
Google::RestApi::Auth - Base class for authorization for Google Rest APIs |
13
|
|
|
|
|
|
|
|
14
|
|
|
|
|
|
|
=head1 DESCRIPTION |
15
|
|
|
|
|
|
|
|
16
|
|
|
|
|
|
|
Small base class that establishes the contract between RestApi and the |
17
|
|
|
|
|
|
|
various possible authorization methods. If the auth class expects to be |
18
|
|
|
|
|
|
|
able to add a param to each URL (outdated), it will be called via 'params' |
19
|
|
|
|
|
|
|
when the time comes to add them to the calling URL. If the auth class |
20
|
|
|
|
|
|
|
expects to add an authorization header, it will be called via 'headers' |
21
|
|
|
|
|
|
|
to return the proper headers for that auth class. |
22
|
|
|
|
|
|
|
|
23
|
|
|
|
|
|
|
The default behaviour is to return nothing for each, so the derived class |
24
|
|
|
|
|
|
|
has to return at least something for one of them to be functional. |