Tim:
Joshua can probably answer best, but I can offer a few broad suggestions:
> So upon executing the asp page, I can output one of three
> different results:
>
> 1) Ok - heres the data
> 2) Nope - user error
> 3) unexpected error occurred
>
> I would normally code 1) into the asp page in question. If condition 2) is
> flagged in the code, can I conditionally <--#include the output
> for case 2?
I suggest that you get comfortable with the $Response->Include("file",
@args) syntax. It allows you to think of include files as subroutines, with
arguments in and return values out. I have also found
$Response->TrapInclude to be very cool also.
In this case, you can centralize all error processing, including sending
email, into a single ASP script called with a $Response->Include or
$Response->TrapInclude.
> As for 3: I want this page to send email to the site administrator as well
> as give the user a descriptive message, so this functionality should be
> available to all pages. I would probably put it in the global.asa (or a
> PerlModule'd module). In this case, I cannot include an asp page.
Take a look at:
$Server->Mail, $Server->RegisterCleanUp and $Response->ErrorDocument.
Getting used to the ASP model takes a while. However, I have found the
transition pleasant and gradual, and once fully adopted, quite productive!
JL
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
