On Sat, Sep 04, 2004 at 03:35:16PM +0100, David R. Baird wrote:
>
> 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.
>
The only situation I've ever run into where the distinction is important
is applications that pass state information in the url, you need to
differentiate if you have forms that look like this:
<DEFANGED_form method=post action="/some/form/action?session=foo&somename=bar">
<input type=text name=somename value="gazonk">
</form>
Without being able to distinguish between the two, you only get one of
the 'somename' parameters.
Addmitedly if your application does this there are better ways to handle
it, but it is something I have run into when dealing with conversion of
legacy applications.
-- Jason Kohles A witty saying proves nothing. email at jasonkohles.com -- Voltaire (1694 - 1778) http://www.jasonkohles.com/_______________________________________________ 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