NAME
Continuity::Request - Simple HTTP::Request-like API for requests inside Continuity
SYNOPSIS
sub main {
my $request = shift;
$request->print("Hello!");
$request->next;
# ...
$name = $request->param('name');
}METHODS
$request->next
Suspend execution until a new Web request is available.
$name = $request->param("name");
Fetch a CGI POST/GET parameter.
@param_names = $request->param();
Fetch a list of posted parameters.
$request->print("Foo!\n");
Write output (eg, HTML).
Since Continuity juggles many concurrent requests, it's necessary to explicitly refer to requesting clients, like $request->print(...), rather than simply doing print ....
$request->set_cookie(CGI->cookie(...));
$request->set_cookie(name => 'value');
Set a cookie to be sent out with the headers, next time the headers go out (next request if data has been written to the client already, otherwise this request). (May not yet be supported by the FastCGI adapter yet.)
$request->uri();
Straight from HTTP::Request, returns a URI object. (Probably not yet supported by the FastCGI adapter.)
$request->method();
Returns 'GET', 'POST', or whatever other HTTP command was issued. Continuity currently punts on anything but GET and POST out of paranoia.
$request->send_headers("X-HTTP-Header: blah\n", $h2)
Send this in the headers
INTERNAL METHODS
$request->send_basic_header();
Continuity does this for you, but it's still part of the API of Continuity::Request objects.
$request->end_request();
Ditto above.
$request->send_static();
Controlled by the staticp => sub { ... } argument pair to the main constructor call to Continuity->new().
DESCRIPTION
This module contains no actual code. It only establishes and documents the interface actually implemented in Continuity::Adapt::FCGI, Continuity::Adapt::HttpDaemon, and, perhaps eventually, other places.