On 5/12/04 12:30 PM, Dave Rolsky wrote: > On Wed, 12 May 2004, John Siracusa wrote: >>> You must call clean_request_args() on the ApacheHandler object at the end of >>> the request, unless you are making a new ApacheHandler object for every >>> request. Otherwise bad things will happen. >>> >>> This is lame, so if someone thinks of a better way to do this, I'd be happy >>> to >>> hear about it. >> >> In my massively more complicated (in both the good and bad senses of the >> word), but spiritually similar Mason-using WebApp framework, I do something >> like this: > > [ much stuff snipped ] > > I think one of the reasons you can do your stuff that way is that you are > using the Mason Interp object to dispatch to Mason, rather than the > ApacheHandler object. Mason's ApacheHandler has no mechanism for being > handed a set of arguments, it insists on getting them itself (from an > Apache::Request or CGI object), which is a little annoying. > > I hope to make ApacheHandler a little less self-contained in the next > major release (1.4), but for now I'm stuck with nasty hacks.
...which begs the question, why not use an interp in MasonX::WebApp instead of trying to wedge in behind Mason's ApacheHandler? After all, I think that's the advice you originally gave me way back when... :) -John -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
