A couple of recent patches are playing around with $r->{query} and
$r->{params}. Would it not be more sensible for Maypole to combine
both GET and POST parameters into a single set, and put them in
$r->{params}, and forget about $r->{query} altogether?
That happens to be what Mason does, and therefore what
MasonX::Maypole does. I've never come across a programming situation
where I made decisions based on whether parameters arrived via POST
or GET, but maybe someone can suggest an example where that would be
important.
d.
-- Dr. David R. Baird Riverside Content Management Systems http://www.riverside-cms.co.uk_______________________________________________ maypole-dev mailing list maypole-dev at lists.netthink.co.uk http://lists.netthink.co.uk/listinfo/maypole-dev
This archive was generated by hypermail 2.1.3 : Thu Feb 24 2005 - 22:25:56 GMT