Re: Intentional Premature Finish in an Apache Module

1999-11-01 Thread Doug MacEachern
On Mon, 1 Nov 1999, John Siracusa wrote: On 11/1/99 2:32 AM, Doug MacEachern wrote: or use this undocumented feature: $Apache::ERRSV_CAN_BE_HTTP = 1; #set this anywhere, startup script is best die FORBIDDEN; mod_perl peeks at $@, if it's a 3 digit http status code, it propagates

Re: Intentional Premature Finish in an Apache Module

1999-10-31 Thread Doug MacEachern
On Thu, 28 Oct 1999, Public Interactive wrote: I'd like to be able to prematurely end the thread of execution within a Perl apache module from someplace *other than* the PerlHandler entry point subroutine (usually "handler()"). That is, when I'm a few subroutines deep inside my module, I

Re: Intentional Premature Finish in an Apache Module

1999-10-28 Thread Public Interactive
On 10/28/99 12:34 PM, Eric Cholet wrote: You could use "eval" and "die", Perl's standard exception mechanism. I thought of that, but I was concerned that my module would suffer a performance hit. Granted, it's not a strong eval, but it just seems ugly. If that's the only way, I guess I'm

Re: Intentional Premature Finish in an Apache Module

1999-10-28 Thread Ken Y. Clark
On Thu, 28 Oct 1999, Public Interactive wrote: I'd like to be able to prematurely end the thread of execution within a Perl apache module from someplace *other than* the PerlHandler entry point subroutine (usually "handler()"). That is, when I'm a few subroutines deep inside my module, I

Re: Intentional Premature Finish in an Apache Module

1999-10-28 Thread John Siracusa
On 10/28/99 1:31 PM, Ken Y. Clark wrote: for what it's worth, here's what i do: [snip] my $err = $r-pnotes(ERROR_NAME) or return OK; Speaking of pnotes(), how stable, API-wise, is it? It isn't documented at all in the O'Reilly Apache Modules book, but I was very happy to find it in the