Thanks for the reply Joe. Yes I do have the Mason book, in fact it is the very
example you point out that made me doubt myself, submiting from login.html to
login_submit.html.
Seeing this I thought perhaps to keep in best practices with Mason I would need
2 pages for all forms, one to collect the data and another to submit to and
process. It just seemed like a complicated process especially if I need to then
redirect to the first page to point out errors in the form.
I think I handle my site login similiar to the way you do. I handle Auth and
session info with the PerlHandler and redirect to the requested page once the
user has successfully authenticated.
I'm glad to hear I'm not breaking any cardnial rules with Mason, I live in a
bubble around here, I don't have any people I can bounce these questions off of
other than the Internet :).
If I understand you OK then I will keep POSTing directly to my pages that
required form data to be entered and perform validation on the same page.
I have the basic framework of the site completed and operational and I just
didn't want to spend all of this time writing the meat of the site only to
discover I went about it wrong.
Thanks,
Tom
> From: [EMAIL PROTECTED]> To: [EMAIL PROTECTED]> Subject: Re: [Mason] Proper
> way to process a submited form> Date: Sun, 19 Oct 2008 10:03:16 -0400> > On
> 18 Oct 2008, Tom Jefferson wrote:> > > I realize there may not be one right
> answer but I would like to hear> > from other people if there is a preferred
> method.> > I think it depends on the architecture of the site. The Mason
> book> (you /do/ have the Mason book, right?) has a full site example in it.>
> For logging in, they submit from login.html to login_submit.html,>
> redirecting from there as needed. In a project I'm doing I submit my> login
> to the page that I redirect to, and handle the actual login in> the
> syshandler (a paradigm that I think I lifted from RT; I can't> remember). If
> there are any errors, I redirect back to the login page.> > My user edit
> page, though, redirects to itself, as I want it> redisplayed whether there
> were problems or not. I try to be cognizant> of the state in which I leave
> the browser, so that the user can hit> Refresh and not resubmit the form
> (unless that's the appropriate thing> to do). It's sometimes tricky to decide
> which is the right state to> leave the user in.> > --> Regards,> > > joe> Joe
> Casadonte> [EMAIL PROTECTED]> >
> ------------------------------------------------------------------------------>
> Llama Fresh Farms => http://www.northbound-train.com> Ramblings of a Gay Man
> => http://www.northbound-train.com/ramblings> Emacs Stuff =>
> http://www.northbound-train.com/emacs.html> Music CD Trading =>
> http://www.northbound-train.com/cdr.html>
> ------------------------------------------------------------------------------>
> Live Free, that's the message!>
> ------------------------------------------------------------------------------
_________________________________________________________________
Store, manage and share up to 5GB with Windows Live SkyDrive.
http://skydrive.live.com/welcome.aspx?provision=1?ocid=TXT_TAGLM_WL_skydrive_102008
-------------------------------------------------------------------------
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
