No ... I think you understand CGI::Application ... but your confusing runmodes with the view portion of MVC - runmodes map to controller methods, not views. So from the scenario you present, I'm not seeing anything out of the ordinary.

update:: Have you taken a look at CGI::Application's homepage and mailing list archive?

update again: Specifically, this thread

sub rm2_method {
  my $self = shift;
  my $username = $self->query->param('user');
  my $password = $self->query->param('pass');
  return $self->rm1_method() unless defined $username and defined $pas
+sword;

  $self->authenticate() ? $self->rm4_method() : $self->rm3_method();
}
[download]

use CGI::Application::Plugin::Forward;
sub rm2_method {
  my $self = shift;
  my $username = $self->query->param('user');
  my $password = $self->query->param('pass');
  return $self->rm1_method() unless defined $username and defined $pas
+sword;

  $self->authenticate() ? $self->forward(rm4') : $self->forward('rm3')
+;
}
[download]

But for me, I won't provide rm3 and rm4. I would probably just use the first approach, by calling other methods (not runmode methods) according to the authentication result. Speaking of which, I would just probably using the authentication plugin.

You can also find numerous discussions from super search (don't forget to click the Search button).