I'm used to write two runmodes for every panel in my application. In your case, they would be login and login_update. Given a method redirect to set the appropriate headers, the code could be the following (not-so-pseudo-code):
# Does nothing except printing the form.
# Using sessions you can pass to it an error_message,
# for example.
#
sub login
+
{
my $self = shift;
+
my $tmpl = $self->load_tmpl( 'login' );
+
return $tmpl->output();
+
}
sub login_update
+
{
my $self = shift;
+
my $q = $self->query;
# Fetch username and password from the form
#
if ( PASSWORD CORRECT ) {
$self->redirect( { rm => 'first_panel' } );
}
else {
# It could store some useful info in a session,
# for example the error message.
#
$self->redirect( { rm => 'login' } );
}
return;
}
I use this technique a lot, and it has proven its flexibility and
efficiency.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|