Hi Elizabeth --
> I have a very similar application and the same set of issues.
> Additionally,
> I have a small concern about using CGI_APP_RETURN_ONLY since
> the comment
> that goes along with it is "serious debug mode only". It
> strikes me that
> this variable was used for developement of CGI::Application
> and it may not
> be very clean to use it in production. Does anyone want to
> comment on the
> long-term use of this the variable?
Yeah: Don't do it. It's for "serious debug mode, only". I may change it
at any time. Out of spite. :-)
> HOWEVER, this has to ultimately be the wrong answer because
> it just doesn't
> allow for clean upgrades to new versions of CGI::App. Unless there is
> interest in making the seperation or run() into action() and ouput() a
> permanent thing.? Or something like it?
Why is it important to separate "action" from "output"? According to HTTP,
every request must return output. Even a redirect requires some output.
It's considered an HTTP error to NOT return output!
Give me a use-case where you would be interested in purposely causing an
error.
If you have some case where you want an "ACTION" with no "OUTPUT", I
recommend this: Call exit(0) at the end of your run-mode instead of
returning data!
sub my_no_output_run_mode {
my $self = shift;
# Do some task which for some reason
# Should never even say, "Ok, it has been done."
exit(0);
}
There you do. No output!
Maybe you have a better example I'm not thinking of?
-Jesse-
----
Jesse Erlbaum, CTO
Vanguard Media
212.242.5317 x115
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
