Re^4: Learning mod

yep that is true, but most of time ppl write scripts directly using some framework like Apache::ASP, Apache::Registry, Apache::Perlrun etc.. instead of writing mod_perl handlers directly...:")

I wasn't trying to say that the other frameworks were bad, just that the "wrapped in sub" thing is not always true. It only applies to certain ways of implementing handlers.

(I'm also not sure that "most" people use these method. You can't really leverage all of the power of mod_perl until you get beyond Apache::Registry and friends. I rarely use them myself.)

Even if mod_perl stays the same, just with one simple options it can be done so that ppl may choose between these 2 variants... it is just a matter of string concatenation...

Sorry. No idea what you mean here.

Comment on Re^4: Learning mod_perl

Replies are listed 'Best First'.
Re: Re^4: Learning mod_perl by bugsbunny (Scribe) on Jul 15, 2003 at 11:33 UTC
i mean that it would be fairly easy to change say Apache::Registry so that it can work in one of the two modes i.e. closure/non-closure way.. 'cause it is a matter of different way of concatenation of strings, before compiling the script..	[reply]
Re^6: Learning mod_perl by adrianh (Chancellor) on Jul 15, 2003 at 12:54 UTC
Sorry, still not getting what you mean. There is no way of avoiding the closure issue. By definition mod_perl handlers are subroutines - you can't get around it - so there is no way to avoid closures if you're just wrapping existing code.	[reply]