Re: [cgiapp] prerun and errormode handling

[Lee Carmichael <suppressed>]

Hello James,


> just curious. why are you using the Dev version of CGI-Application-4.07_01? it doesn't seem to

> have  any advantages to me.


Sorry for the confusion but we aren't using the development release. We
are using 4.06. I didn't want to go through the work of writing a patch
for 4.06 if there weren't any plans for another release or writing a
patch for 4.06 and forcing someone else to port the change forward.


I guess I was asking more about the release plans for cgiapp 4.07 vs 4.06 but not in a very clear way. :)


> regarding trapping errors, usually the failures from cgiapp_prerun/setup are unexpected system

> errors. I let apache handle that (use ErrorDocument)


As for 'setup' errors, I agree that they would be better handled by something else. But I have some items that seem to make sense to validate inside of cgiapp_prerun method. My understanding with ErrorDocument is that it doesn't pass any real message to your page. (for example: if database connection is down call dba's vs. filesystem is missing call sysadmins, it just calls a page for 500's or such.).

Thinking a bit more about it, I guess I could do something like:

sub cgiapp_prerun { 
   my $self  = shift;
   
   eval { $self->validate_env(); };
   my $err = $@;

   if ( $err) { 
      $self->param('error_msg', $err );
      $self->prerun_mode( 'error' );
   } 

}

but this seems a bit wrong. 

Take Care,

Lee
 


---------------------------------------------------------------------
Web Archive:  http://www.mail-archive.com/suppressed/
              http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: suppressed
For additional commands, e-mail: suppressed