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

Re: Intentional Premature Finish in an Apache Module

1999-11-01 Thread John Siracusa
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 > that value to Apache. Sounds great, but I'

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 Andrei A. Voropaev
On Thu, Oct 28, 1999 at 02:07:12PM -0400, Ken Y. Clark wrote: > > when i tried to assign my error intothe pnotes hash with the comma operator > e.g., "$r->pnotes(ERROR_NAME =>$err)" > i got errors, and i don't know why. Oh, that's because everything to the left of => is treated as string un

RE: Intentional Premature Finish in an Apache Module

1999-10-28 Thread Young, Geoffrey S.
mod_perl source Changes. --Geoff > -Original Message- > From: John Siracusa [SMTP:[EMAIL PROTECTED]] > Sent: Thursday, October 28, 1999 1:50 PM > To: [EMAIL PROTECTED] > Subject: Re: Intentional Premature Finish in an Apache Module > > On 10/28/99 1:31 PM, Ken Y.

Re: Intentional Premature Finish in an Apache Module

1999-10-28 Thread John Siracusa
On 10/28/99 2:07 PM, Ken Y. Clark wrote: > pnotes seems stable to me. i believe it's capable of holding some pretty > dense data structures -- surely much more than my measly error > string. Oh yeah, I've got a whole big structure hanging off a single pnotes() entry. It's very convenient :) >

Re: Intentional Premature Finish in an Apache Module

1999-10-28 Thread Ken Y. Clark
On Thu, 28 Oct 1999, John Siracusa wrote: > 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

RE: Intentional Premature Finish in an Apache Module

1999-10-28 Thread Eric Cholet
> >>> 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 stuck, but it seems >

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 Apac

Re: Intentional Premature Finish in an Apache Module

1999-10-28 Thread Public Interactive
On 10/28/99 1:26 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 g

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 Eric Cholet
> > 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 stuck, but it seems I don't see wh

Re: Intentional Premature Finish in an Apache Module

1999-10-28 Thread Autarch
On Thu, 28 Oct 1999, Public Interactive wrote: > 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

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 stuc

RE: Intentional Premature Finish in an Apache Module

1999-10-28 Thread Eric Cholet
> 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 want to be able > to spit out an error page and