Parent Directory
| 
Revision Log
++ manakai/lib/Message/ChangeLog 11 Aug 2007 13:36:49 -0000 2007-08-11 Wakaba <wakaba@suika.fam.cx> * Makefile: New directory |CGI| is added. 2007-08-11 Wakaba <wakaba@suika.fam.cx> * CGI/: New directory. ++ manakai/lib/Message/CGI/ChangeLog 11 Aug 2007 13:33:26 -0000 * Makefile: New file. * HTTP.pm: Reformed for manakai. 2007-08-11 Wakaba <wakaba@suika.fam.cx>
| 1 | wakaba | 1.1 | <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> |
| 2 | <html xmlns="http://www.w3.org/1999/xhtml"> | ||
| 3 | <head> | ||
| 4 | <title>Message::CGI::HTTP - An Object-Oriented HTTP CGI Interface</title> | ||
| 5 | <link rel="stylesheet" href="http://suika.fam.cx/www/style/html/pod.css" type="text/css" /> | ||
| 6 | <link rev="made" href="mailto:[email protected]" /> | ||
| 7 | </head> | ||
| 8 | |||
| 9 | <body> | ||
| 10 | |||
| 11 | <p><a name="__index__"></a></p> | ||
| 12 | <!-- INDEX BEGIN --> | ||
| 13 | |||
| 14 | <ul> | ||
| 15 | |||
| 16 | <li><a href="#name">NAME</a></li> | ||
| 17 | <li><a href="#description">DESCRIPTION</a></li> | ||
| 18 | <li><a href="#methods">METHODS</a></li> | ||
| 19 | <li><a href="#todo">TODO</a></li> | ||
| 20 | <li><a href="#see_also">SEE ALSO</a></li> | ||
| 21 | <li><a href="#author">AUTHOR</a></li> | ||
| 22 | <li><a href="#license">LICENSE</a></li> | ||
| 23 | </ul> | ||
| 24 | <!-- INDEX END --> | ||
| 25 | |||
| 26 | <hr /> | ||
| 27 | <p> | ||
| 28 | </p> | ||
| 29 | <h1><a name="name">NAME</a></h1> | ||
| 30 | <p>Message::CGI::HTTP - An Object-Oriented HTTP CGI Interface</p> | ||
| 31 | <p> | ||
| 32 | </p> | ||
| 33 | <hr /> | ||
| 34 | <h1><a name="description">DESCRIPTION</a></h1> | ||
| 35 | <p>The <code>Message::CGI::HTTP</code> module provides an object-oriented | ||
| 36 | interface for inputs and outputs as defined by CGI specification.</p> | ||
| 37 | <p>This module is part of manakai.</p> | ||
| 38 | <p> | ||
| 39 | </p> | ||
| 40 | <hr /> | ||
| 41 | <h1><a name="methods">METHODS</a></h1> | ||
| 42 | <dl> | ||
| 43 | <dt><strong><a name="item_new"><em>$cgi</em> = Message::CGI::HTTP->new;</a></strong><br /> | ||
| 44 | </dt> | ||
| 45 | <dd> | ||
| 46 | Creates and returns a new instance of HTTP CGI interface object. | ||
| 47 | </dd> | ||
| 48 | <p></p> | ||
| 49 | <dt><strong><a name="item_get_meta_variable"><em>$value</em> = <em>$cgi</em>->get_meta_variable (<em>$name</em>)</a></strong><br /> | ||
| 50 | </dt> | ||
| 51 | <dd> | ||
| 52 | Returns the value of the meta-variable <em>$name</em>. The name | ||
| 53 | specified by the <em>$name</em> SHOULD be a meta-variable name | ||
| 54 | defined by a CGI specification, e.g. <code>CONTENT_TYPE</code> or | ||
| 55 | <code>HTTP_USER_AGENT</code>. Otherwise, the result is implementation | ||
| 56 | dependent. In an environment where meta-variables are supplied | ||
| 57 | as envirnoment variables, specifying an environment variable | ||
| 58 | that is not a meta-variable, such as <code>PATH</code>, results in the | ||
| 59 | value of that environment variable. However, CGI scripts | ||
| 60 | SHOULD NOT depend on such behavior. | ||
| 61 | </dd> | ||
| 62 | <dd> | ||
| 63 | <p>This method might return <code>undef</code> when the meta-variable | ||
| 64 | is not defined or is defined but its value is <code>undef</code>.</p> | ||
| 65 | </dd> | ||
| 66 | <p></p> | ||
| 67 | <dt><strong><a name="item_meta_variable_names"><em>$list</em> = <em>$cgi</em>->meta_variable_names;</a></strong><br /> | ||
| 68 | </dt> | ||
| 69 | <dd> | ||
| 70 | Returns list of meta variables. Note that this list might contain | ||
| 71 | other environmental variables than CGI meta variables, since | ||
| 72 | they cannot distinglish unless we know what is CGI meta variable | ||
| 73 | and what is not. Unfortunately, there is no complete list of CGI | ||
| 74 | meta variables, whilst list of standarized meta variables is available. | ||
| 75 | </dd> | ||
| 76 | <dd> | ||
| 77 | <p>NOTE: Some application might use an environmental variable named | ||
| 78 | 'HTTP_HOME', which might make some confusion with CGI meta variable | ||
| 79 | for HTTP 'Home:' header field. Fortunately, such name of HTTP | ||
| 80 | header field is not intoroduced as far as I kn |