Simon Flack:
> But not for param(). param() IMO, should call $r->get_request->param(). That'd
> work at least for Apache::MVC and CGI::Maypole. You'd probably need something
> cleverer for Maypole::CLI.
Huh? No, I think you misunderstand.
The intention was that a Maypole request should be a superset of an
Apache::Request or equivalent. It should encapsulate everything you need to
know about the journey of a request from the browser to Maypole and out
through the view class and the frontend. The parameters and arguments are no
longer Apache or CGI parameters and arguments - they are Maypole parameters
and arguments. You don't need to care where they come from.
Imagine a pure-Maypole httpd (in a week, you won't have to *imagine* one,
since I actually need one) - it won't get_request because the Maypole request
will be all there is.
get_request merely merges information from the environment into the Maypole
request object.
-- Imbalance of power corrupts and monopoly of power corrupts absolutely. -- Genji
This archive was generated by hypermail 2.1.3 : Thu Feb 24 2005 - 22:25:56 GMT