Eric Andreychek > OpenPlugin-0.11 > OpenPlugin::Request

Download:
OpenPlugin-0.11.tar.gz

Dependencies

Annotate this POD

CPAN RT

New  2
Open  0
View/Report Bugs
Module Version: 1.07   Source  

NAME ^

OpenPlugin::Request - Retrieve values related to the client request

SYNOPSIS ^

 my $r = shift;
 $OP = OpenPlugin->new( request => { apache => $r });

 ...

 my $req_obj = $OP->request->object;
 my $uri     = $OP->request->uri;

DESCRIPTION ^

The Request plugin offers an interface to retrieve various pieces of information available regarding the client request.

If you're looking for methods to work with params, cookies, headers, or uploads, so those respective plugins.

This plugin acts as somewhat of a superclass of those plugins, and offers you access to the request object, along with a variety of other methods.

METHODS ^

object()

Returns the request object.

uri()

Returns the uri for the last request.

BUGS ^

None known.

TO DO ^

The interface provided by the Request/Cookie/Httpheader/Param/Upload plugins, is, as you know, meant to abstract the existing CGI and mod_perl interfaces (along with any other drivers that may, at one day, be created). The interface provided here is certainly not complete. What other functionality should we provide here?

Making the developer access the request object breaks the abstraction OpenPlugin provides. The more accessor functions we provide, the better, it would seem.

Another thing we are doing now is allowing, say, the httpheader plugin to use the CGI driver, and the param plugin the Apache driver. Is this useful? Some things could be made simpler both internally and externally if we eliminate that possibility, and have httpheader/param/cookie/upload all automatically use the same driver.

As an alias for get_incoming/set_incoming, we provide get/set. There are some who also might like a method called incoming, that acts differently depending on if parameters were passed in or not. OTOH, having too many different interfaces may just confuse the matter.

I'm also considering providing a mechanism for retrieving a tied hash. Instead of using the above interface, you would just add or remove items from the tied hash. Very similar to Apache::Table.

It would be neat to have more drivers. How about a POE driver? CGI::Request, CGI::Base, CGI::MiniSvr, and others would also be neat.

There are Param and HttpHeader drivers for mod_perl 2.x. The Cookie and Upload drivers don't exist yet, hopefully they will soon. Feel free to contribute them :-)

SEE ALSO ^

See the individual driver documentation for settings and parameters specific to that driver.

COPYRIGHT ^

Copyright (c) 2001-2003 Eric Andreychek. All rights reserved.

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

AUTHORS ^

Eric Andreychek <eric@openthought.net>

syntax highlighting: