I generally prefer to post to the same URL as I serve the form from,
although you can always put up a dumb form elsewhere (perhaps with
default values specific to that URL's purpose) and have it post to the
primary form handler's URL. You can skip processing by watching for
whatever criteria you like;
if (%ARGS != 0)
might be better than
if ($ARGS{'submit'})
if you accept GET parameters. Or watch for some token parameter you send
from valid submission locations (which is a good way to pre-populate a
form partially without having validation errors pop up the first time it
gets displayed.) Use whatever seems easiest for you.
> you might want to reduce the load on the server by doing client-side
> checking with Javascript.
javascript grooming is a nice addition for user convenience, but you shouldn't
trust the data to have come from where it should have, so you still need to do
all actual validation server side regardless. 'Taint safe to trust user data.
RJ Herrick
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Mason-users mailing list
Mason-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mason-users
