Codebase list libcgi-psgi-perl / HEAD
HEAD

Tree @HEAD (Download .tar.gz) 

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
NAME
    CGI::PSGI - Adapt CGI.pm to the PSGI protocol

SYNOPSIS
      use CGI::PSGI;

      my $app = sub {
          my $env = shift;
          my $q = CGI::PSGI->new($env);
          return [ $q->psgi_header, [ $body ] ];
      };

DESCRIPTION
    This module is for web application framework developers who currently
    uses CGI to handle query parameters, and would like for the frameworks
    to comply with the PSGI protocol.

    Only slight modifications should be required if the framework is already
    collecting the body content to print to STDOUT at one place (rather
    using the print-as-you-go approach).

    On the other hand, if you are an "end user" of CGI.pm and have a CGI
    script that you want to run under PSGI web servers, this module might
    not be what you want. Take a look at CGI::Emulate::PSGI instead.

    Your application, typically the web application framework adapter should
    update the code to do "CGI::PSGI->new($env)" instead of "CGI->new" to
    create a new CGI object. (This is similar to how CGI::Fast object is
    initialized in a FastCGI environment.)

INTERFACES SUPPORTED
    Only the object-oriented interface of CGI.pm is supported through
    CGI::PSGI. This means you should always create an object with
    "CGI::PSGI->new($env)" and should call methods on the object.

    The function-based interface like "use CGI ':standard'" does not work
    with this module.

METHODS
    CGI::PSGI adds the following extra methods to CGI.pm:

  env
      $env = $cgi->env;

    Returns the PSGI environment in a hash reference. This allows
    CGI.pm-based application frameworks such as CGI::Application to access
    PSGI extensions, typically set by Plack Middleware components.

    So if you enable Plack::Middleware::Session, your application and plugin
    developers can access the session via:

      $cgi->env->{'plack.session'}->get("foo");

    Of course this should be coded carefully by checking the existence of
    "env" method as well as the hash key "plack.session".

  psgi_header
     my ($status_code, $headers_aref) = $cgi->psgi_header(%args);

    Works like CGI.pm's header(), but the return format is modified. It
    returns an array with the status code and arrayref of header pairs that
    PSGI requires.

    If your application doesn't use "$cgi->header", you can ignore this
    method and generate the status code and headers arrayref another way.

  psgi_redirect
     my ($status_code, $headers_aref) = $cgi->psgi_redirect(%args);

    Works like CGI.pm's redirect(), but the return format is modified. It
    returns an array with the status code and arrayref of header pairs that
    PSGI requires.

    If your application doesn't use "$cgi->redirect", you can ignore this
    method and generate the status code and headers arrayref another way.

AUTHOR
    Tatsuhiko Miyagawa <miyagawa@bulknews.net>

    Mark Stosberg <mark@summersault.com>

LICENSE
    This library is free software; you can redistribute it and/or modify it
    under the same terms as Perl itself.

SEE ALSO
    CGI, CGI::Emulate::PSGI

Commit History @HEAD